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. Mine currently looks like: trusted_networks 64.71.152.40 208.93.0.48 trusted_network docs: http://spamassassin.apache.org/full/3.3.x/doc/Mail_SpamAssassin_Conf.html#network_test_options http://wiki.apache.org/spamassassin/TrustPath The change was on the server end, so the previous version of the plugin will work. The new version of the plugin also tells you the IP that was reported: http://www.chaosreigns.com/dnswl/dl/DNSWLh.pm You can also check the IP that was reported on http://www.dnswl.org/abuse/pastreports.pl ( http//www.dnswl.org / Report Abuse, Report / History ) If you have any problems, just email adm...@dnswl.org (or me, but I'm on that list). Just a repeat of the instructions: --------------------------------------------------------------- Download http://www.chaosreigns.com/dnswl/dl/DNSWLh.pm to /usr/share/perl5/Mail/SpamAssassin/Plugin/ (or your equivalent) In your spamassassin config, add the following three lines: loadplugin Mail::SpamAssassin::Plugin::DNSWLh dnswl_address u...@example.com dnswl_password yourpassword --------------------------------------------------------------- Note: This new feature, using trusted_networks, does not apply to using the web form directly, since SpamAssassin doesn't insert the header. This is what actually gets reported (I'm adding the three headers at the top): http://www.chaosreigns.com/dnswl/dnswlbody.1267458909.txt Currently, it only reads X-Spam-Relays-Untrusted if the Content-Description header is first, to avoid spammer forgeries. -- "Anarchy is based on the observation that since few are fit to rule themselves, even fewer are fit to rule others." -Edward Abbey http://www.ChaosReigns.com
