From: Mail Delivery Subsystem <MAILER-DAEMON@awing.netscape.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] Returned mail: see transcript for details
Date: Thu, 21 Aug 2003 11:21:30 -0700 [thread overview]
Message-ID: <200308211821.h7LILUdi000319@awing.netscape.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
The original message was received at Thu, 21 Aug 2003 11:17:54 -0700 (PDT)
from adsl-68-20-119-158.dsl.sfldmi.ameritech.net [68.20.119.158]
----- The following addresses had permanent fatal errors -----
<yeungkw1731t76@netscape.com>
(reason: 550 5.1.1 <yeungkw1731t76@netscape.com>... User unknown)
----- Transcript of session follows -----
... while talking to shemail.aoltw.net.:
>>> RCPT To:<yeungkw1731t76@netscape.com>
<<< 550 5.1.1 <yeungkw1731t76@netscape.com>... User unknown
550 5.1.1 <yeungkw1731t76@netscape.com>... User unknown
[-- Attachment #2: Type: message/delivery-status, Size: 423 bytes --]
[-- Attachment #3.1: Type: text/plain, Size: 210 bytes --]
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: text/rfc822-headers
[-- Attachment #3.2: file.suspect --]
[-- Type: application/octet-stream, Size: 665 bytes --]
Received: from TRU-TEMPHVAC (adsl-68-20-119-158.dsl.sfldmi.ameritech.net [68.20.119.158])
by awing.netscape.com (8.12.8/8.12.8) with ESMTP id h7LIHmdi029814
for <yeungkw1731t76@netscape.com>; Thu, 21 Aug 2003 11:17:54 -0700 (PDT)
Message-Id: <200308211817.h7LIHmdi029814@awing.netscape.com>
From: <9fans@cse.psu.edu>
To: <yeungkw1731t76@netscape.com>
Subject: Your details
Date: Thu, 21 Aug 2003 2:18:03 --0400
X-MailScanner: Found to be clean
Importance: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MSMail-Priority: Normal
X-Priority: 3 (Normal)
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="_NextPart_000_063E4227"
next reply other threads:[~2003-08-21 18:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 18:21 Mail Delivery Subsystem [this message]
2003-08-21 23:33 Mail Delivery Subsystem
2004-06-13 22:35 Mail Delivery Subsystem
2004-06-15 2:00 Mail Delivery Subsystem
2004-07-26 14:49 archivist
2004-07-26 15:01 Mail Administrator
2004-07-26 15:09 Bounced mail
2004-07-26 15:12 melanie
2004-07-26 15:13 [9fans] RETURNED MAIL: SEE TRANSCRIPT FOR DETAILS drake
2004-07-26 15:23 [9fans] Returned mail: see transcript for details wglunz
2004-07-26 15:37 Mail Delivery Subsystem
2004-07-26 15:44 assistance
2004-07-26 15:44 donange
2004-07-26 15:46 Mail Administrator
2004-07-26 15:49 fberruet
2004-07-26 15:51 hetz
2004-07-26 15:54 fandrade
2004-07-26 15:54 Returned mail
2004-07-26 15:55 [9fans] RETURNED MAIL: SEE TRANSCRIPT FOR DETAILS aleman
2004-07-26 15:57 [9fans] Returned mail: see transcript for details dstanton
2004-07-26 15:59 djbakker
2004-07-26 16:02 moreinfo
2004-07-26 16:03 qdlss
2004-07-26 16:04 The Post Office
2004-07-26 16:07 Mail Administrator
2004-07-26 16:41 ia
2004-07-26 16:48 Automatic Email Delivery Software
2004-07-26 16:55 [9fans] RETURNED MAIL: SEE TRANSCRIPT FOR DETAILS j.koenig57
2004-07-26 17:42 [9fans] Returned mail: see transcript for details jdicianni
2004-07-26 17:52 The Post Office
2004-07-26 18:08 Mail Delivery Subsystem
2004-07-26 18:40 Returned mail
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=200308211821.h7LILUdi000319@awing.netscape.com \
--to=mailer-daemon@awing.netscape.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).