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: Thu, 26 Jun 2003 06:08:59 -0400	[thread overview]
Message-ID: <200306261008.GAC18363@rly-xd01.mx.aol.com> (raw)

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

The original message was received at Thu, 26 Jun 2003 06:08:12 -0400 (EDT)
from 209-242-9-175.dls.net [209.242.9.175]


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

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

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

[-- Attachment #3: Type: message/rfc822, Size: 114894 bytes --]

[-- Attachment #3.1.1: Type: text/plain, Size: 45 bytes --]

Please see the attached zip file for details.

[-- Attachment #3.1.2.1: Type: text/plain, Size: 346 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: application/x-zip-compressed;
	name="your_details.zip"
	Content-Transfer-Encoding: base64
	Content-Disposition: attachment;
	filename="your_details.zip

[-- Attachment #3.1.2.2.1: Type: text/plain, Size: 277 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: application/octet-stream
	Content-Disposition: attachment; filename="your_details.zip

[-- Attachment #3.1.2.2.2: "your_details.zip --]
[-- Type: application/octet-stream, Size: 82195 bytes --]

             reply	other threads:[~2003-06-26 10:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-26 10:08 Mail Delivery Subsystem [this message]
2003-08-20 14:33 Mail Delivery Subsystem
2003-08-20 21:20 Mail Delivery Subsystem
2003-08-21  1:20 Mail Delivery System
2003-08-21  3:29 Mail Delivery Subsystem
2003-08-21 12:36 Mail Delivery System
2003-08-21 12:43 Mail Delivery System
2003-08-21 19:43 Mail Delivery System
2003-08-21 23:13 Mail Delivery Subsystem
2003-08-22  4:44 Mail Delivery Subsystem
2003-08-22  5:26 Mail Delivery System
2004-06-02 16:45 Mail Delivery Subsystem
2004-06-02 16:46 Mail Delivery Subsystem
2004-06-11 15:30 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=200306261008.GAC18363@rly-xd01.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).