Stan Hoeppner skrev den 2013-10-12 18:26:
FSL_HELO_BARE_IP_2 needs to have a -much- lower score, or be
eliminated
entirely, as it overlaps with at least 3 other tests, as pointed out
previously by another user. If a message makes it through Gmane, and
Debian, and then gets flagged by my "stock" rules introduced through
an
auto update, then something is obviously wrong.
problem is that one in the chain of delivery mail used a ip in helo it
does not matter that debian did not here, hmm :)
ask debian maillist maintainers to create a bug for missing spf and
dkim ?, so receipients can whitelist something from this maillist ?
remember spamaassassin does not block, it just scores, if scores are
incorrect add more rules to help it score right will do
Content analysis details: (4.8 points, 4.2 required)
2.8 FSL_HELO_BARE_IP_2 FSL_HELO_BARE_IP_2
1.2 RCVD_NUMERIC_HELO Received: contains an IP address used for
HELO
0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60%
[score: 0.5314]
yep a overlap, but still under 5.0 in score ?
for the overlap create a bug might help more
