On lør 25 sep 2010 06:00:13 CEST, Karsten Bräckelmann wrote
user_in_whitelist includes whitelist_from with can be forged, my fav
to be removed if i just can convence more devs :)
Bug number? Sorry, getting late here, too lazy to search whether you
actually filed it. ;)
okay i will create a ticket, as i am the only one that dont use
whitelist_from *...@hotmail.com
spammers using it and get caught on spf
createing a ticket gave me this error:
undef error - Can't locate Class/Singleton.pm in @INC (@INC contains:
. lib /x1/issues/htdocs/SpamAssassin
/x1/issues/htdocs/SpamAssassin/lib/sun4-solaris-thread-multi-64
/x1/issues/htdocs/SpamAssassin/lib
/opt/perl5/lib/5.10.1/sun4-solaris-thread-multi-64
/opt/perl5/lib/5.10.1
/opt/perl5/lib/site_perl/5.10.1/sun4-solaris-thread-multi-64
/opt/perl5/lib/site_perl/5.10.1
/usr/local/apache2-install/issues.apache.org-bugzilla/current) at
/opt/perl5/lib/site_perl/5.10.1/DateTime/TimeZone/Europe/Copenhagen.pm
line 14. BEGIN failed--compilation aborted at
/opt/perl5/lib/site_perl/5.10.1/DateTime/TimeZone/Europe/Copenhagen.pm
line 14. Compilation failed in require at (eval 5248) line 3
ticket summary: perldoc Mail::SpamAsssassin::Conf whitelist_from
should not be an option
ticket text:
there is to much errors that goes back to this "option" and it serves
no spam test at all, so imho it could be removed without any problem
to still detect spam
maybe it could just be recoded to give another score for whitelist ?
but as it is now it gives -100 when fired on a maybe 100% forged mail :(
silly, RFC :)there is to much errors that goes back to this "option"
and it serves no spam test at all, so imho it could be removed without
any problem to still detect spam
maybe it could just be recoded to give another score for whitelist ?
but as it is now it gives -100 when fired on a maybe 100% forged mail :(
silly, RFC :)
--
xpoint http://www.unicom.com/pw/reply-to-harmful.html
