> https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6508
> > In my experience this has been an important feature.
> > I know of a number of people that have setups like this:
> > trusted_networks 10.20.30.0/24
> > internal_networks 10.20.30.0/24 !10.20.30.2/31
> > Where the /24 covers their MXes and the /31 covers their MSAs.
>
> The above produces a lint warning:
>
> $ spamassassin --lint
> warn: netset: cannot exclude 10.20.30.2/31 as it has already been included
Right after me commenting on the bug, I started to wonder and was just
about to ask... What's the purpose of negation, if it generates a lint
warning and claims it cannot be done?
The docs told me. :)
Daryl's example probably just was manually typed in a hurry. The docs
say the order is important, and must be reversed. Should work as meant
otherwise.
"If a network or host address is prefaced by a ! the network or host
will be excluded (or included) in a first listed match fashion."
The respective example also shows more specific negation first, then the
broader inclusion. Right?
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
