This rule seems not to apply when the subject is encoded It is identifying this message as having lots of white space on its subject:
Subject: *****SPAM***** =?iso-8859-1?B?RXNwYedvIG5vIHNlcnZpZG9y?= It also complains about the date, saying it has AM/PM Date: Tue, 7 May 2002 09:12:46 -0300 (Hora padrão leste da Am. Sul) Shouldn't the rule ignore what's between parenthesis? Correct me if I am wrong, but I think the parens are used for comments, aren't they? Am. in the case above is short for "America". Here's the report: X-Spam-Report: Detailed Report SPAM: -------------------- Start SpamAssassin results ---------------------- SPAM: This mail is probably spam. The original message has been altered SPAM: so you can recognise or block similar unwanted mail in future. SPAM: See http://spamassassin.org/tag/ for more details. SPAM: SPAM: Content analysis details: (5.7 hits, 5 required) SPAM: Hit! (3.2 points) Invalid Date: header (has AM/PM) SPAM: Hit! (2.5 points) Subject contains lots of white space SPAM: SPAM: -------------------- End of SpamAssassin results --------------------- -- Eduardo Marcel Maçan Gerente de Redes / Network Manager [EMAIL PROTECTED] Colégio Bandeirantes _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
