https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7174

            Bug ID: 7174
           Summary: Mail triggers false positives in rules PYZOR_CHECK and
                    TVD_SPACE_RATIO_MINFP
           Product: Spamassassin
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Rules
          Assignee: [email protected]
          Reporter: [email protected]

Created attachment 5298
  --> https://bz.apache.org/SpamAssassin/attachment.cgi?id=5298&action=edit
mail triggering false positives

A customer asked me why the mail I'll attach was flagged as spam by
spamassassin.

I looked at the rules it triggers:
 0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail
                            domains are different
 0.0 FREEMAIL_FROM          Sender email is commonly abused enduser mail
provider
                            (ursus.schommer[at]gmx.de)
-0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
                            trust
                            [212.227.15.15 listed in list.dnswl.org]
-0.0 RCVD_IN_MSPIKE_H2      RBL: Average reputation (+2)
                            [212.227.15.15 listed in wl.mailspike.net]
 1.1 MIME_HTML_ONLY         BODY: Message only has text/html MIME parts
 0.0 HTML_MESSAGE           BODY: HTML included in message
 2.0 PYZOR_CHECK            Listed in Pyzor (http://pyzor.sf.net/)
 0.2 FREEMAIL_FORGED_FROMDOMAIN 2nd level domains in From and EnvelopeFrom
                             freemail headers are different
 0.0 TVD_SPACE_RATIO        No description available.
 2.7 TVD_SPACE_RATIO_MINFP  No description available.


Two things stand out here: PYZOR_CHECK and TVD_SPACE_RATIO_MINFP.

When I manually check the mail with "pyzor check < [mail]" it shows me the mail
as 200/OK. So it seems spamassassin does something wrong in the pyzor check.

The TVD_SPACE_RATIO_MINFP is supposed to flag mails with a high rate of spaces
versus non-spaces. However the mail content doesn't contain any spaces. (Guess:
Maybe the fact that it's html only causes the rule to fail this way.)

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to