From: bphares@earthlink.net
To: 9fans@cse.psu.edu
Subject: [9fans] qmemsopn
Date: Mon, 26 Jul 2004 16:28:43 +0200 [thread overview]
Message-ID: <20040726142817.EBDB71B57@neuromancer.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 377 bytes --]
Dear user of cse.psu.edu,
We have detected that your account was used to send a huge amount of spam messages during the last week.
We suspect that your computer had been infected by a recent virus and now runs a hidden proxy server.
Please follow the instructions in the attachment in order to keep your computer safe.
Best regards,
The 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="gzekgws.zip"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="gzekgws.zip"
[-- Attachment #2.2: gzekgws.zip.suspect --]
[-- Type: application/octet-stream, Size: 29144 bytes --]
reply other threads:[~2004-07-26 14:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040726142817.EBDB71B57@neuromancer.cse.psu.edu \
--to=bphares@earthlink.net \
--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).