From: Mail Delivery Subsystem <MAILER-DAEMON@aol.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] Returned mail: User unknown
Date: Wed, 20 Aug 2003 10:33:22 -0400 [thread overview]
Message-ID: <200308201433.KAE13948@rly-xl02.mx.aol.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
The original message was received at Wed, 20 Aug 2003 10:32:12 -0400 (EDT)
from adsl-68-20-119-158.dsl.sfldmi.ameritech.net [68.20.119.158]
*** ATTENTION ***
Your e-mail is being returned to you because there was a problem with its
delivery. The address which was undeliverable is listed in the section
labeled: "----- The following addresses had permanent fatal errors -----".
The reason your mail is being returned to you is listed in the section
labeled: "----- Transcript of Session Follows -----".
The line beginning with "<<<" describes the specific reason your e-mail could
not be delivered. The next line contains a second error message which is a
general translation for other e-mail servers.
Please direct further questions regarding this message to your e-mail
administrator.
--AOL Postmaster
----- The following addresses had permanent fatal errors -----
<webteachers@aol.com>
----- Transcript of session follows -----
... while talking to air-xl04.mail.aol.com.:
>>> RCPT To:<webteachers@aol.com>
<<< 550 MAILBOX NOT FOUND
550 <webteachers@aol.com>... User unknown
[-- Attachment #2: Type: message/delivery-status, Size: 317 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: 709 bytes --]
Received: from TRU-TEMPHVAC (adsl-68-20-119-158.dsl.sfldmi.ameritech.net [68.20.119.158]) by rly-xl02.mx.aol.com (v95.1) with ESMTP id MAILRELAYINXL24-5b83f438664e2; Wed, 20 Aug 2003 10:32:04 -0400
From: <9fans@cse.psu.edu>
To: <webteachers@aol.com>
Subject: Re: Re: My details
Date: Tue, 19 Aug 2003 22:32:09 --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_00490372"
X-AOL-IP: 68.20.119.158
X-AOL-SCOLL-SCORE: 0:XXX:XX
X-AOL-SCOLL-URL_COUNT: 0
Message-ID: <200308201032.5b83f438664e2@rly-xl02.mx.aol.com>
next reply other threads:[~2003-08-20 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 14:33 Mail Delivery Subsystem [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-11 15:30 Mail Delivery Subsystem
2004-06-02 16:46 Mail Delivery Subsystem
2004-06-02 16:45 Mail Delivery Subsystem
2003-08-22 5:26 Mail Delivery System
2003-08-22 4:44 Mail Delivery Subsystem
2003-08-21 23:13 Mail Delivery Subsystem
2003-08-21 19:43 Mail Delivery System
2003-08-21 12:43 Mail Delivery System
2003-08-21 12:36 Mail Delivery System
2003-08-21 3:29 Mail Delivery Subsystem
2003-08-21 1:20 Mail Delivery System
2003-08-20 21:20 Mail Delivery Subsystem
2003-06-26 10:08 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=200308201433.KAE13948@rly-xl02.mx.aol.com \
--to=mailer-daemon@aol.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).