[an error occurred while processing this directive]
Spam detection software, running on the system "rimantadine.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: (18.7 points, 4.9 required)
pts rule name description
---- ---------------------- --------------------------------------------------
1.0 NO_REAL_NAME From: does not include a real name
3.1 MSGID_SHORT Message-ID is unusually short
0.1 FORGED_RCVD_HELO Received: contains a forged HELO
1.5 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO
0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines
3.5 BAYES_99 BODY: Bayesian spam probability is 99 to 100%
[score: 1.0000]
2.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address
[72.129.109.19 listed in dnsbl.sorbs.net]
0.2 DNS_FROM_RFC_ABUSE RBL: Envelope sender in abuse.rfc-ignorant.org
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
2.2 INVALID_MSGID Message-Id is not valid, according to RFC 2822
0.8 AWL AWL: From: address is in the auto white-list
--- Begin Message ---
- From: service@intl.paypal.com
- Date: Fri, 1 Sep 2006 09:02:17 -0500
--- End Message ---