...
If you admin a SpamAssassin installation and suspect something in the configuration may be wrong, see here: AvoidingFpsForAdmins
If you are the recipient, simply add that sender to your ManualWhitelist. (You could also change the score of the rules that were triggered. See WritingRules).
FORGED_JUNO_RCVD is broken
I just now noticed that email from my friends who use Juno is being marked as spam. They hit the
| No Format |
|---|
2.8 FORGED_JUNO_RCVD 'From' juno.com does not match 'Received' headers
2.4 OPT_HEADER Headers include an "opt"ed phrase
|
rules, which is already 5.2 points.
| No Format |
|---|
Received: (from [[my friend at]]juno.com)
by webmail03.lax.untd.com (jqueuemail) id JN4CHC6U; Mon, 23 Feb 2004 09:05:53 PST
Received: from [199.245.163.1] by webmail03.lax.untd.com with HTTP:
Mon, 23 Feb 2004 17:05:40 GMT
X-Originating-IP: [199.245.163.1]
Mime-Version: 1.0
X-Original-From: "[[my friend at]]juno.com" <[[my friend at]]juno.com>
Date: Mon, 23 Feb 2004 17:05:40 GMT
To: [[DavidCary at]]ieee.org
Subject: Bolivar
X-Mailer: WebMail Version 2.0
Content-Type: text/plain
From: [[my friend at]]juno.com
Message-Id: <20040223.090553.5165.1153023@webmail03.lax.untd.com>
X-ContentStamp: 2:2:815233092
X-UCE-Filter-Settings: david_cary redirected to 90_OPT_OUT
X-Scanned-By: IEEE UCE Filtering Service
|
Currently I work around this by setting
| No Format |
|---|
score FORGED_JUNO_RCVD 1
score OPT_HEADER 0
|
but someone 
really should fix the FORGED_JUNO_RCVD rule so it does *not* trigger on mail that truly does come from innocent Juno users.
...