9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: kpei@lucent.com
To: 9fans@cse.psu.edu
Subject: [9fans] Message could not be delivered
Date: Mon, 26 Jul 2004 11:52:15 -0400	[thread overview]
Message-ID: <200407261552.i6QFqHe5011465@ihemail2.lucent.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 721 bytes --]

The message was not delivered due to the following reason(s):

Your message could not be delivered because the destination server was
unreachable within the allowed queue period. The amount of time
a message is queued before it is returned depends on local configura-
tion parameters.

Most likely there is a network problem that prevented delivery, but
it is also possible that the computer is turned off, or does not
have a mail system running right now.

Your message was not delivered within 2 days:
Server 50.78.123.198 is not responding.

The following recipients did not receive this message:
<9fans@cse.psu.edu>

Please reply to postmaster@lucent.com
if you feel this message to be in error.


[-- Attachment #2.1: Type: text/plain, Size: 351 bytes --]

from postmaster@ethel:
The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: application/octet-stream;
	name="text.zip"
	Content-Transfer-Encoding: base64
	Content-Disposition: attachment;
	filename="text.zip"

[-- Attachment #2.2: text.zip.suspect --]
[-- Type: application/octet-stream, Size: 29222 bytes --]

             reply	other threads:[~2004-07-26 15:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26 15:52 kpei [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-26 18:41 sooner
2004-07-26 18:13 Automatic Email Delivery Software
2004-07-26 16:29 dtaskent
2004-07-26 16:07 frank
2004-07-26 15:55 Returned mail
2004-07-26 15:52 b.ralley
2004-07-26 15:50 shimes
2004-07-26 15:50 venezio
2004-07-26 15:43 david.zyble
2004-07-26 15:00 community

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=200407261552.i6QFqHe5011465@ihemail2.lucent.com \
    --to=kpei@lucent.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).