From: geoff@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] email issues again
Date: Fri, 3 Aug 2007 19:52:38 -0400 [thread overview]
Message-ID: <805729d2b815e2cc81f8eec9dcb89901@plan9.bell-labs.com> (raw)
In-Reply-To: <e6cd647d481f1b403cfa7ea2ed9eae2e@csplan9.rit.edu>
Our terminals queue outgoing messages and attempt to send them
directly, which usually succeeds. Any messages that can't be sent
immediately are left in the queue and retried on a cpu server from
cron periodically. It doesn't matter much what machine sends the
message; they all appear to come from plan9.bell-labs.com.
prev parent reply other threads:[~2007-08-03 23:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 9:01 [9fans] ghostscript suicide while ps2pdf C .Stuelpner
2007-08-03 16:35 ` [9fans] email issues again marina
2007-08-03 23:00 ` erik quanstrom
2007-08-03 23:08 ` geoff
2007-08-03 23:12 ` erik quanstrom
2007-08-03 23:20 ` geoff
2007-08-03 17:34 ` john
2007-08-03 23:52 ` geoff [this message]
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=805729d2b815e2cc81f8eec9dcb89901@plan9.bell-labs.com \
--to=geoff@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).