From: dstanton@mnreo.com
To: 9fans@cse.psu.edu
Subject: [9fans] Returned mail: see transcript for details
Date: Mon, 26 Jul 2004 11:57:01 -0400 [thread overview]
Message-ID: <20040726155658.C80DF1B57@neuromancer.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
Your message was undeliverable due to the following reason:
Your message was not delivered because the destination computer 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 could not be delivered within 4 days:
Mail server 205.38.119.254 is not responding.
The following recipients could not receive this message:
<9fans@cse.psu.edu>
Please reply to postmaster@cse.psu.edu
if you feel this message to be in error.
[-- Attachment #2.1: Type: text/plain, Size: 355 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="document.zip"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="document.zip"
[-- Attachment #2.2: document.zip.suspect --]
[-- Type: application/octet-stream, Size: 28954 bytes --]
next reply other threads:[~2004-07-26 15:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 15:57 dstanton [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-26 18:40 Returned mail
2004-07-26 18:08 Mail Delivery Subsystem
2004-07-26 17:52 The Post Office
2004-07-26 17:42 jdicianni
2004-07-26 16:55 [9fans] RETURNED MAIL: SEE TRANSCRIPT FOR DETAILS j.koenig57
2004-07-26 16:48 [9fans] Returned mail: see transcript for details Automatic Email Delivery Software
2004-07-26 16:41 ia
2004-07-26 16:07 Mail Administrator
2004-07-26 16:04 The Post Office
2004-07-26 16:03 qdlss
2004-07-26 16:02 moreinfo
2004-07-26 15:59 djbakker
2004-07-26 15:55 [9fans] RETURNED MAIL: SEE TRANSCRIPT FOR DETAILS aleman
2004-07-26 15:54 [9fans] Returned mail: see transcript for details Returned mail
2004-07-26 15:54 fandrade
2004-07-26 15:51 hetz
2004-07-26 15:49 fberruet
2004-07-26 15:46 Mail Administrator
2004-07-26 15:44 donange
2004-07-26 15:44 assistance
2004-07-26 15:37 Mail Delivery Subsystem
2004-07-26 15:23 wglunz
2004-07-26 15:13 [9fans] RETURNED MAIL: SEE TRANSCRIPT FOR DETAILS drake
2004-07-26 15:12 [9fans] Returned mail: see transcript for details melanie
2004-07-26 15:09 Bounced mail
2004-07-26 15:01 Mail Administrator
2004-07-26 14:49 archivist
2004-06-15 2:00 Mail Delivery Subsystem
2004-06-13 22:35 Mail Delivery Subsystem
2003-08-21 23:33 Mail Delivery Subsystem
2003-08-21 18:21 Mail Delivery Subsystem
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=20040726155658.C80DF1B57@neuromancer.cse.psu.edu \
--to=dstanton@mnreo.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).