From: "Chong Cristal" <venessajeffriescpvodwede@excite.com>
To: "Administrator" <acharya@cse.psu.edu>
Cc: "AOL Users" <9fans@cse.psu.edu>
Subject: [--SPAM--] [9fans] How are you doing
Date: Sat, 14 Feb 2004 07:14:05 -0700 [thread overview]
Message-ID: <0b7501c3f304$cd8f3880$53e608b3@venessajeffriescpvodwede> (raw)
[-- Attachment #1: Type: text/plain, Size: 2236 bytes --]
Spam detection software, running on the system "psuvax1.cse.psu.edu", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or block
similar future email. If you have any questions, see
postmaster@cse.psu.edu for details.
Content preview: Hello, Did you know online gambling software has double
the odds as real life gambling? We will credit your account with two
hundred dollars to play. Don't get played by the house, download our
software: http://www.inboxesoffer.org/AidDownload.php?affidƒ0 [...]
Content analysis details: (17.0 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
1.4 RCVD_FAKE_HELO_DOTCOM Received contains a faked HELO hostname
4.3 RATWARE_RCVD_LC_ESMTP Bulk email fingerprint ('esmtp' Received) found
1.8 DCC_CHECK Listed in DCC (http://rhyolite.com/anti-spam/dcc/)
2.8 FAKE_HELO_EXCITE Host HELO did not match rDNS: excite.com
0.5 RCVD_IN_NJABL_DIALUP RBL: NJABL: dialup sender did non-local SMTP
[151.16.13.77 listed in dnsbl.njabl.org]
0.1 RCVD_IN_SORBS RBL: SORBS: sender is listed in SORBS
[151.16.13.77 listed in dnsbl.sorbs.net]
[68.80.146.41 listed in dnsbl.sorbs.net]
0.1 RCVD_IN_NJABL RBL: Received via a relay in dnsbl.njabl.org
[151.16.13.77 listed in dnsbl.njabl.org]
1.1 RCVD_IN_DSBL RBL: Received via a relay in list.dsbl.org
[<http://dsbl.org/listing?ip=68.80.146.41>]
0.1 RCVD_IN_RFCI RBL: Sent via a relay in ipwhois.rfc-ignorant.org
[Inaccurate or missing WHOIS data]
2.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see <http://www.spamcop.net/bl.shtml?68.80.146.41>]
2.5 RCVD_IN_DYNABLOCK RBL: Sent directly from dynamic IP address
[151.16.13.77 listed in dnsbl.sorbs.net]
[68.80.146.41 listed in dnsbl.sorbs.net]
[-- Attachment #2: original message before SpamAssassin --]
[-- Type: message/rfc822, Size: 2312 bytes --]
From: "Chong Cristal" <venessajeffriescpvodwede@excite.com>
To: "Administrator" <acharya@cse.psu.edu>
Cc: "AOL Users" <9fans@cse.psu.edu>
Subject: [9fans] How are you doing
Date: Sat, 14 Feb 2004 07:14:05 -0700
Message-ID: <0b7501c3f304$cd8f3880$53e608b3@venessajeffriescpvodwede>
Hello,
Did you know online gambling software has double the odds as real life
gambling? We will credit your account with two hundred dollars to play.
Don't get played by the house, download our software:
http://www.inboxesoffer.org/AidDownload.php?affid=830
If you recieved this in error: http://www.in-boxes-offer.org/u.php/
Thanks,
Landon Crouch
reply other threads:[~2004-02-14 14:14 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='0b7501c3f304$cd8f3880$53e608b3@venessajeffriescpvodwede' \
--to=venessajeffriescpvodwede@excite.com \
--cc=9fans@cse.psu.edu \
--cc=acharya@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).