From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan 9 and gmail
Date: Wed, 26 Oct 2005 11:58:43 -0400 [thread overview]
Message-ID: <4af52069343fd570f1953bdbef6029bb@plan9.bell-labs.com> (raw)
In-Reply-To: <a225ec6ae17c8397f109076686673b3c@coraid.com>
On Wed Oct 26 10:07:30 EDT 2005, brantley@coraid.com wrote:
> ...
> i think 1127 gets their mail from the main bell labs mailer.
> ...
No, we use Plan 9. Turns out the Plan 9 mail system can do
things the IT-managed corporate system can't and some of those
things the company relies on.
We haven't seen any problems like those you describe, but I
don't know if we get much traffic from gmail offhand.
--jim
next prev parent reply other threads:[~2005-10-26 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 14:04 Brantley Coile
2005-10-26 14:50 ` Lucio De Re
2005-10-26 15:34 ` Aaron Griffin
2005-10-26 15:38 ` Steve Simon
2005-10-26 15:58 ` jmk [this message]
2005-10-26 17:06 ` Skip Tavakkolian
2005-10-26 17:55 ` Taj Khattra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4af52069343fd570f1953bdbef6029bb@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).