https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7826
--- Comment #89 from Michael Storz <sa-...@lrz.de> --- (In reply to Henrik Krohns from comment #88) > Trunk-welcomelist branch is now merged back to trunk (Revision 1900215) and > deleted. > > Automatic updates has been stopped, tomorrow we see if everything is ok and > a new tarball is generated. Then we can manually wget the tarballs and test > on some installations. Again, note all the 60_welcomelist*.cf etc changes, > everything should be now if can()'d and "enable_compat > welcomelist_blocklist" should disable old rules from running. Good job! I found a few whitelist entries, but they might be intentional: lib/Mail/SpamAssassin/Plugin/DCC.pm See http://www.rhyolite.com/dcc/reputations.html You C<must> whitelist your lib/Mail/SpamAssassin/Plugin/Pyzor.pm whitelisted to the Pyzor server for SpamAssassin to consider ignoring the result. Final decision is made by pyzor_whitelist_factor. Ignore Pyzor result if REPORTCOUNT x NUMBER >= pyzor_whitelist_min. For default setting this means: 50 reports requires 10 whitelistings. lib/Mail/SpamAssassin/Plugin/Razor2.pm # if mail isn't whitelisted, check it out lib/Mail/SpamAssassin/Plugin/FromNameSpoof.pm foreach my $white_addr (keys %{$list_refs->{$owner}}) { if ($check =~ $list_refs->{$owner}{$white_addr}) { rules/60_welcomelist_auth.cf # SpamAssassin rules file: default SPF and DKIM whitelists # SPF and DKIM whitelist rules rules/60_welcomelist_spf.cf # Whitelist and blacklist addresses are now file-glob-style patterns, so ./t/body_str.t: use_auto_whitelist 0 ./t/db_awl_perms.t: use_auto_whitelist 1 ./t/dnsbl_subtests.t:# use_auto_whitelist 0 ./t/dkim.t: use_auto_whitelist 0 ./t/spamd_kill_restart.t: use_auto_whitelist 0 ./t/spamd_kill_restart_rr.t: use_auto_whitelist 0 ./t/spamd_unix.t: use_auto_whitelist 0 ./t/sql_based_whitelist.t: use_auto_whitelist 1 ./t/sql_based_whitelist.t: use_auto_whitelist 1 ./t/whitelist_subject.t: use_auto_whitelist 0 ./masses/bayes-testing/benchmark/tests/db_file/site/local.cf:use_auto_whitelist 0 ./masses/bayes-testing/benchmark/tests/mysql/site/local.cf:use_auto_whitelist 0 ./masses/bayes-testing/benchmark/tests/sdbm/site/local.cf:use_auto_whitelist 0 ./masses/bayes-testing/benchmark/tests/pgsql/site/local.cf:use_auto_whitelist 0 ./masses/bayes-testing/benchmark/tests/bdb/site/local.cf:use_auto_whitelist 0 ./build/automc/run_preflight: use_auto_whitelist 0 ./t.rules/run: post_config_text => "use_learner 0\nuse_auto_whitelist 0\n".$configtext, backend/nitemc/run_one_nitemc: use_auto_whitelist 0 ./t/db_awl_path.t: auto_whitelist_path ./$workdir/awl/shouldbeinaccessible ./t/db_awl_path.t: auto_whitelist_file_mode 0755 ./t/db_awl_perms.t: auto_whitelist_path ./$userstate/awl ./t/db_awl_perms.t: auto_whitelist_file_mode 0755 ./t/sa_awl.t: auto_whitelist_path ./$userstate/awltest ./t/sa_awl.t: auto_whitelist_file_mode 0755 ./t/sql_based_whitelist.t: auto_whitelist_factory Mail::SpamAssassin::SQLBasedAddrList ./t/sql_based_whitelist.t: auto_whitelist_factory Mail::SpamAssassin::SQLBasedAddrList ./sql/README.awl:This is done with the auto_whitelist_factory config variable, like ./sql/README.awl:auto_whitelist_factory Mail::SpamAssassin::SQLBasedAddrList ./sql/README.awl:if auto_whitelist_distinguish_signed is true, e.g. (in local.cf): ./sql/README.awl: auto_whitelist_distinguish_signed 1 ./sql/README.awl: auto_whitelist_distinguish_signed 1 ./UPGRADE - FreeMail: new options freemail_import_whitelist_auth, freemail_import_def_whitelist_auth added (Bug 6451) pyzor_max setting to pyzor_count_min. Added pyzor_whitelist_min and pyzor_whitelist_factor setting. Also try to ignore "empty body" FPs. ./INSTALL will not be suitable for DNS queries and white/blacklisting. -- You are receiving this mail because: You are the assignee for the bug.
