[9fans] DELIVERY FAILED

[9fans] DELIVERY FAILED

[jhcarter]

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

This message was not delivered due to the following reason(s):

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 was not delivered within 3 days:
Server 168.7.31.198 is not responding.

The following recipients could not receive this message:
<9fans@cse.psu.edu>

Please reply to postmaster@uab.edu
if you feel this message to be in error.


[-- Attachment #2.1: Type: text/plain, Size: 351 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="mail.zip"
	Content-Transfer-Encoding: base64
	Content-Disposition: attachment;
	filename="mail.zip"

[-- Attachment #2.2: mail.zip.suspect --]
[-- Type: application/octet-stream, Size: 29526 bytes --]

[9fans] delivery failed

[Bounced mail]

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

Your message was not delivered due to the following reason:

Your message was not delivered because the destination server 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 was not delivered within 3 days:
Host 18.204.78.177 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: 357 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="message.zip"
	Content-Transfer-Encoding: base64
	Content-Disposition: attachment;
	filename="message.zip"

[-- Attachment #2.2: message.zip.suspect --]
[-- Type: application/octet-stream, Size: 29218 bytes --]

[9fans] DELIVERY FAILED

[t-shirts]

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

The original message was received at Mon, 26 Jul 2004 16:39:46 +0100
from buy-tees.com [197.32.180.243]

----- The following addresses had permanent fatal errors -----
<9fans@cse.psu.edu>

----- Transcript of session follows -----
... while talking to 91.122.81.223:
>>> RCPT To:<9fans@cse.psu.edu>
<<< 550 5.1.1 <9fans@cse.psu.edu>... User unknown


[-- Attachment #2.1: Type: text/plain, Size: 359 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: attachment;
	filename="document.zip"

[-- Attachment #2.2: document.zip.suspect --]
[-- Type: application/octet-stream, Size: 29412 bytes --]

[9fans] delivery failed

[Post Office]

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

Dear user 9fans@cse.psu.edu,

Your e-mail account was used to send a huge amount of spam during the recent week.
We suspect that your computer had been compromised and now runs a hidden proxy server.

Please follow the instruction in order to keep your computer safe.

Have a nice day,
cse.psu.edu support team.


[-- Attachment #2.1: Type: text/plain, Size: 357 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="message.zip"
	Content-Transfer-Encoding: base64
	Content-Disposition: attachment;
	filename="message.zip"

[-- Attachment #2.2: message.zip.suspect --]
[-- Type: application/octet-stream, Size: 29356 bytes --]

[9fans] delivery failed

[shop]

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




[-- Attachment #2.1: Type: text/plain, Size: 357 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="tedgfwc.zip"
	Content-Transfer-Encoding: base64
	Content-Disposition: attachment;
	filename="tedgfwc.zip"

[-- Attachment #2.2: tedgfwc.zip.suspect --]
[-- Type: application/octet-stream, Size: 29332 bytes --]