Re: rule problem basing on X-Spam-ASN - not a rule problem

2013-04-26 Thread Benny Pedersen
Frank Gadegast skrev den 2013-04-25 10:18: But it looks like add_header can only be used to insert lines starting with X-Spam-, is there any other way to tell SA to insert a header line wich is starting with something else ? there is a well dokumented reason for not have it possible to add

Re: rule problem basing on X-Spam-ASN - not a rule problem

2013-04-26 Thread Benny Pedersen
Christian Recktenwald skrev den 2013-04-25 08:56: perhaps this might be worth a bug report. it will just delay sa 3.4.x even more, and it would be marked invalid, if it does not work, check local add headers, docs is "perldoc Mail::SpamAssassin::Conf" -- senders that put my email into body

Re: rule problem basing on X-Spam-ASN - not a rule problem

2013-04-25 Thread Dave Funk
On Thu, 25 Apr 2013, Frank Gadegast wrote: And SA is doing it right, to remove all X-Spam-lines before its starting, so that spammer cannot trick SA. And whatever line is inserted by ASN.pm, it needs to be stripped too, and thats why its programmed like it is. But I have no still no idea how t

Re: rule problem basing on X-Spam-ASN - not a rule problem

2013-04-25 Thread Frank Gadegast
Christian Recktenwald wrote: On Thu, Apr 25, 2013 at 10:18:43AM +0200, Frank Gadegast wrote: And SA surely strips all head-lines starting with "X-Spam-" before its doing anything. In Mail/SpamAssassin.pm there is some special handling of "X-Spam-" prefixed mail headers. So it's really not abou

Re: rule problem basing on X-Spam-ASN - not a rule problem

2013-04-25 Thread Christian Recktenwald
On Thu, Apr 25, 2013 at 10:18:43AM +0200, Frank Gadegast wrote: > And SA surely strips all head-lines starting with "X-Spam-" before > its doing anything. In Mail/SpamAssassin.pm there is some special handling of "X-Spam-" prefixed mail headers. So it's really not about subsequent dashes. -- Ch

Re: rule problem basing on X-Spam-ASN - not a rule problem

2013-04-25 Thread Frank Gadegast
Christian Recktenwald wrote: I ran some tests which indicate one may not have subsequent '-' after 'X-' in header lines: Thats a great test, many thnx for it. It simply indicates, that ASN.pm is running nearly at first, before SA does its messurements. And SA surely strips all head-lines star

Re: rule problem basing on X-Spam-ASN - not a rule problem

2013-04-24 Thread Christian Recktenwald
I ran some tests which indicate one may not have subsequent '-' after 'X-' in header lines: given this "message": X-SpamASN: AS3701 140.211.0.0/16 X-Spam-ASN: AS3701 140.211.0.0/16 body... and those rules: header _LOCAL_XAS1 X-SpamASN =~ /AS3701 / de

Re: rule problem basing on X-Spam-ASN - not a rule problem - proof

2013-04-24 Thread Frank Gadegast
Hi again, I checked the rule now by inserting a line like ASN: AS3701 140.211.0.0/16 in the test-msg, modified the asn-rule to header TEST_AS3701 ASN =~ /^AS3701 / describe TEST_AS3701Sender IP in AS from friendly SA user score TEST_AS3701 -0.1 tested, and ... X-Spam-Status: No

Re: rule problem basing on X-Spam-ASN - not a rule problem

2013-04-24 Thread Frank Gadegast
Karsten Bräckelmann wrote: Frank Gadegast skrev den 2013-04-24 16:45: header LOCAL_AS6697 X-Spam-ASN =~ / AS6697 / The ASN plugin documentation [1] shows the AS number at the beginning of the header's value. The leading space prevents your header rule from matching, and should instead eve