You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2009/09/11 21:38:41 UTC

[Bug 6196] FH_HELO_ENDS_DOT rule is overly aggressive in assigning a spam score

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6196


John Hardin <jh...@impsec.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jhardin@impsec.org




--- Comment #1 from John Hardin <jh...@impsec.org>  2009-09-11 12:38:39 PST ---
(In reply to comment #0)
>
> One of the cPanel developers has weighed in on the issue in the aforementioned
> URL

The URL fell off your post.

> and believes that the rule in question
> scores matching headers far too heavily given that a FQDN technically is
> supposed to end in a dot in the first place.

As has been mentioned before elsewhere, SA is not a standards-compliance
auditing tool. The score is based on that pattern appearing in actual spams and
not appearing in actual hams, regardless of whether or not it is syntactically
valid. At the moment the corpora contain almost no ham having that pattern, so
it looks like a strong spam indicator and is thus scored rather heavily. 

If you can attach some FP examples to this bug, they could be added to the
corpora.

The score generation process for 3.3.0 is underway right now; I don't know
whether your report made the cutoff for adjusting this rule's score or not -
Justin? Is this too late to address in the 3.3.0 release?

Your customer could also just fix the HELO that their MTA sends and omit the
trailing period... :)

-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.