Hi.

I’m using SA with MdF on Linux (Fedora 22).

MdF generates the header “Return-Path: <mail-from>” for me, so that should be 
available to me in the rules.

To test this, I wrote a couple of rules:

header __L_EMPTY_SENDER         EnvelopeFrom:addr !~ /./
header __L_MATCH_SENDER         EnvelopeFrom:addr =~ /.*/

I’ve also tried:

header __L_EMPTY_SENDER         EnvelopeFrom:addr =~ /^$/

but in all cases, I get:

Sep 22 11:07:46.237 [26384] dbg: rules: ran header rule __L_EMPTY_SENDER 
======> got hit: "negative match"
Sep 22 11:07:46.237 [26384] dbg: rules: ran header rule __L_MATCH_SENDER 
======> got hit: "negative match”

which I don’t get, because other similar rules end up showing what $& (or 
${^MATCH}) would be (i.e. what matched).

What is a negative match, anyway?  Looking at the code, it seems that 
::hit_rule_plugin_code() only gets called when we matched anyway, so saying 
it’s a negative match is counter-intuitive.

Am I seeing https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6360 in this 
case?  And comment 2 says:

  trunk (3.4.0):


  Bug 6360
  : "negative match" on a "0" string - not fixed,
    appears cosmetic, just added a comment
  Sending lib/Mail/SpamAssassin/Plugin/Check.pm
  Committed 
  revision 1338300.

but the bug is marked “RESOLVED FIXED” so I’m confused.  Should it be “WONTFIX” 
instead?

Thanks,

-Philip

Reply via email to