Hello Dave, Wednesday, January 26, 2005, 9:49:40 AM, you wrote:
DSFRS> Once 3.02 was installed, I sent myself something that should be DSFRS> detected as spam yet it wasn't. Here is the header: DSFRS> X-Spam-Status: No, score=3.1 required=4.0 tests=ALL_TRUSTED,AWL, DSFRS> DEEP_DISC_MEDS,DRUGS_ANXIETY,DRUGS_ANXIETY_EREC,DRUGS_DIET, DSFRS> DRUGS_ERECTILE,DRUGS_MANYKINDS,DRUGS_MUSCLE,DRUGS_PAIN, DSFRS> DRUG_ED_GENERIC,DRUG_ED_ONLINE,NO_REAL_NAME,UPPERCASE_25_50 DSFRS> autolearn=no version=3.0.2 And, why would an email sent by YOU be considered spam? ALL_TRUSTED indicates that the email came from/through trusted links. It could indicate that the email never left your system. It significantly lowers the score of the email. DSFRS> I have "use_auto_whitelist 0" in my user_prefs so why is there DSFRS> a hit on AWL? Answered by Matt. DSFRS> Is ALL_TRUSTED telling me that because it came from me, it's DSFRS> assumed to be ham? That's my interpretation, that plus the AWL (the source of the mail, you, normally do not send spam, and so AWL greatly lowers the scores of emails you send). The correct test for this is to use the command > spamassassin <emailfile >outputfile and then look at the output file to see if the spam was identified correctly. Since you haven't emailed or forwarded or redirected or done anything else with the file that would change the headings, the scoring should be a whole lot more accurate. Once you pass that test, the second test is to look at the headers of mail that comes in from outside your system, both spam and non-spam, and see if the headers and scoring is correct. (You can't tell me that you had to go back weeks to find this spam -- you probably receive one or two of those a day, no?) Bob Menschel
