9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mail Delivery Subsystem <MAILER-DAEMON@aol.com>
To: <9fans@cse.psu.edu>
Subject: [9fans] Returned mail: User unknown
Date: Wed,  2 Jun 2004 12:46:33 -0400	[thread overview]
Message-ID: <200406021646.MAD22470@rly-yj02.mx.aol.com> (raw)

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

The original message was received at Wed, 2 Jun 2004 12:45:53 -0400 (EDT)
from las-dsl115-cust035.mpowercom.net [208.57.115.35]


*** 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 -----
<readapear@aol.com>

   ----- Transcript of session follows -----
... while talking to air-yj01.mail.aol.com.:
>>> RCPT To:<readapear@aol.com>
<<< 550 MAILBOX NOT FOUND
550 <readapear@aol.com>... User unknown

[-- Attachment #2: Type: message/delivery-status, Size: 313 bytes --]

[-- Attachment #3.1: Type: text/plain, Size: 234 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: text/rfc822-headers

[-- Attachment #3.2: file.suspect --]
[-- Type: application/octet-stream, Size: 651 bytes --]

Received: from  aol.com (las-dsl115-cust035.mpowercom.net [208.57.115.35]) by rly-yj02.mx.aol.com (v99_r4.3) with ESMTP id MAILRELAYINYJ23-7f940be043f27c; Wed, 02 Jun 2004 12:45:52 -0400
From: 9fans@cse.psu.edu
To: readapear@aol.com
Subject: Mail Delivery (failure readapear@aol.com)
Date: Wed, 2 Jun 2004 09:37:46 -0700
MIME-Version: 1.0
Content-Type: multipart/related;
	type="multipart/alternative";
	boundary="----=_NextPart_000_001B_01C0CA80.6B015D10"
X-Priority: 3
X-MSMail-Priority: Normal
X-AOL-IP: 208.57.115.35
X-AOL-SCOLL-SCORE: 1:XXX:XX
X-AOL-SCOLL-URL_COUNT: 1
Message-ID: <200406021245.7f940be043f27c@rly-yj02.mx.aol.com>

             reply	other threads:[~2004-06-02 16:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02 16:46 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: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-08-20 14:33 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=200406021646.MAD22470@rly-yj02.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).