On Mon, 2011-12-12 at 11:50 -0800, Ted Mittelstaedt wrote:
> I concur 100%. Daniel is wrong. The problem isn't
> dnswl.org the problem is the person who made the decision in
> SpamAssassin to have the default for the dnswl plugin ENABLED
Please don't forget that this became an issue only after DNSWL policy
change. At the time the DNSWL rules have been enabled by default in SA,
there where no deliberately false listing responses.
> by default. That decision has been recognized to have been a
> mistake which is why SA is making an update that will
> turn it off by default.
Not a mistake -- but a dangerous rule to ship in the face of the DNSWL
policy change.
> This is not a "blame the user for stupid configuration mistakes"
> problem this is a "blame the software developer for a stupid
> configuration mistake" And the software developer has
> acknowledged it was a mistake. So why people are calling
> SA users "abusive" is beyond me.
See above, not a mistake.
And I don't see anyone calling the users abusive. But the DNS servers.
Which is causing collateral damage to some users.
--
char *t="\10pse\0r\0dtu\0.@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; }}}
