On Sep 23, 2015, at 6:35 AM, RW <rwmailli...@googlemail.com> wrote: > On Tue, 22 Sep 2015 11:43:18 -0600 > Philip Prindeville wrote: > >> 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 think you're going to kick yourself. ".*" ,means zero or more > characters, so matches anything. > > It looks like the superfluous "*" is the only thing wrong here.
No, I wanted to match the entirety of the Return-Path to see what it contained, and that SA was parsing it correctly… Using -D would allow me to see what the rule held as the match-string… except that wasn’t working due to bug 6360. Thanks Martin for fixing that so quickly! Just wanted to make sure that it wasn’t something silly like including a leading space, for example. > > >> What is a negative match, anyway? > > AFAIK it just means that the rule matched without matching any actual > text for the debug to display. > > >> Am I seeing https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6360 >> in this case? > > This looks to be a bug where "negative match" is also displayed if the > matched text is "0", i.e. the number zero rather than a null string. Yeah, exactly. Or if you’re matching against the empty string… I.e.: EnvelopeFrom:addr =~ /^$/ -Philip
