[an error occurred while processing this directive]
Spam detection software, running on the system "amantadine.ncsa.uiuc.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 label
similar future email. If you have any questions, see
postmaster@ncsa.uiuc.edu for details.
Content preview: [...]
Content analysis details: (15.4 points, 4.9 required)
pts rule name description
---- ---------------------- --------------------------------------------------
1.0 NO_REAL_NAME From: does not include a real name
0.1 FORGED_RCVD_HELO Received: contains a forged HELO
1.4 MSGID_FROM_MTA_ID Message-Id for external message added locally
1.0 BAYES_60 BODY: Bayesian spam probability is 60 to 80%
[score: 0.6063]
0.2 DNS_FROM_RFC_ABUSE RBL: Envelope sender in abuse.rfc-ignorant.org
1.6 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see <http://www.spamcop.net/bl.shtml?66.64.10.18>]
1.5 RCVD_IN_SORBS_WEB RBL: SORBS: sender is a abuseable web server
[66.64.10.18 listed in dnsbl.sorbs.net]
1.8 MISSING_SUBJECT Missing Subject: header
2.3 EMPTY_MESSAGE Message appears to be empty with no Subject: text
0.1 TO_CC_NONE No To: or Cc: header
4.4 AWL AWL: From: address is in the auto white-list
--- Begin Message ---
- From: acc-overview@paypal.com
- Date: Thu, 14 Sep 2006 22:36:21 -0500
--- End Message ---