On Tue, 2010-03-02 at 10:32 -0500, dar...@chaosreigns.com wrote:
> If you have spamassassin's trusted_networks value configured properly, this
> module will now always report the correct IP to DNSWL when you run
> spamassassin --report.
>
> trusted_networks needs to be right for all DNS Blacklist checks (and DNSWL)
> to know which IP to check.
Yes, this is crucial as I mentioned a few times on a previous thread.
The obvious ones (to the admin) are *known* forwarders, e.g. alias
addresses implemented using .forward or similar. Less obvious ones
include role accounts for mailing lists (owner-foo@). These servers
usually do not *originate* the spam...
Probably often forgotten or overlooked ones include mailing list
servers. If ML traffic is scanned.
All these might be obvious to the admin -- IFF he knows about them. But
does he know about all lists his users might be on? Good to think about
this for admins with a large-ish or anonymous user base before reporting
stuff to DNSWL.
guenther
--
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; }}}
