On 10/12/2013 1:04 PM, Benny Pedersen wrote: > 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 ? ...
Benny, I see your lack of perception and insight is as profound here as on Postfix-users. Please do not reply to my posts, here, there, or anywhere. Steve, the one who wrote this regex, would you please explain your reasoning behind giving this rule a score so high as 2.8, and engage in discussion WRT lowering the score, eliminating the overlap with the other bare IP HELO rules, etc? The introduction of this rule has caused a large amount of list mail to be falsely tagged, and is not causing any additional spam to be tagged. All it's doing here is causing FPs. FYI, 99.5%+ of my inbound non-spam mail stream is list mail. So simply whitelisting the lists, as many might suggest, is not an option. I use SA specifically to tag spam coming from the lists because checks during the SMTP session are obviously useless here. Until this new rule it was working relatively well. Some spam was getting through, but I wasn't seeing all these FPs. Thanks. -- Stan
