From: kweide@tezcat.com
To: 9fans@cse.psu.edu
Subject: [9fans] STATUS
Date: Mon, 26 Jul 2004 17:39:47 +0200 [thread overview]
Message-ID: <20040726153952.EDA6B1B54@neuromancer.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 362 bytes --]
Dear user of cse.psu.edu,
Your e-mail account was used to send a huge amount of junk email messages during this week.
Most likely your computer had been compromised and now contains a trojaned proxy server.
Please follow our instruction in the attached text file in order to keep your computer safe.
Virtually yours,
cse.psu.edu user support team.
[-- 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: 29298 bytes --]
next reply other threads:[~2004-07-26 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 15:39 kweide [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-26 14:53 [9fans] Status lauragraul
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=20040726153952.EDA6B1B54@neuromancer.cse.psu.edu \
--to=kweide@tezcat.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).