Gary, Gary V <lists <at> johnmecham.com> writes: > > It seems that Amavis or SpamAssassin are ignoring the $sa_* settings in the > > configuration files, no matter what I change. > Then I suspect you have a procmail recipe or other program calling > spamassassin after it leaves amavisd-new. > grep 'SPAM FROM' /etc/spamassassin/local.cf
nothing. But in /etc/amavis/en_US/template-spam-admin.txt > Is spamd running? It should not be if you are using amavisd-new for > spam scanning. If it is running it may indicate some program has been > using it. Yes, it was - I've now disabled spamd. > amavisd-new stop > amavisd-new debug-sa >/var/lib/amavis/1.log 2>&1 & > wait 15 seconds > send a test message (not gtube) and wait about 40 seconds > amavisd-new stop > amavisd-new start > less /var/lib/amavis/1.log As far as I can tell the log seems to be okay: http://asterix.ifusion.de/amavis.log > Are you running amavisd-new chrooted? > grep daemon_chroot_dir /etc/amavis/conf.d/* No, it's Debian default. > I suggest you also set: > <at> debug_sender_maps = ( ['fbn <at> thelogic.org'] ); Hm this does not look so good (this is just a cut): amavis[12119]: (12119-01) SpamControl: calling spam scanner amavis[12119]: (12119-01) spam_scan: DSPAM not available, skipping it amavis[12119]: (12119-01) timer set to 320 s for SA (was 480 s) amavis[12119]: (12119-01) calling SA parse, SA version 3.1.0 amavis[12119]: (12119-01) CALLING SA check amavis[12119]: (12119-01) prolong_timer spam_scan_sa_finish: timer set to = 476 s amavis[12119]: (12119-01) spam_scan: score=0 tests=[none] amavis[12119]: (12119-01) prolong_timer spam_scan: remaining time = 476 s Mamavis[12119]: (12119-01) lookup: (scalar) matches, result="10" amavis[12119]: (12119-01) lookup (spam_kill_level) => true, "[EMAIL PROTECTED]" matches, result="10", matching_key="(constant:10)" amavis[12119]: (12119-01) query_keys: [EMAIL PROTECTED], fbn@, thelogic.org, .thelogic.org, .org, . amavis[12119]: (12119-01) lookup_hash([EMAIL PROTECTED]), no matches amavis[12119]: (12119-01) lookup (bypass_spam_checks) => undef, "[EMAIL PROTECTED]" does not match amavis[12119]: (12119-01) lookup: (scalar) matches, result="5" amavis[12119]: (12119-01) lookup (spam_tag2_level) => true, "[EMAIL PROTECTED]" matches, result="5", matching_key="(constant:5)" amavis[12119]: (12119-01) final_destiny PASS, recip [EMAIL PROTECTED] > You should check for any amavisd-new errors in your mail.log: > grep '!' /var/log/mail.log Only one entry from today: May 12 00:47:47 asterix amavis[12119]: (12119-01) (!) PRESERVING EVIDENCE in /var/lib/amavis/tmp/amavis-20060512T004743-12119 > The Debian 2.3 and 2.4 versions of amavisd-new ignore amavisd.conf. If > you are in fact using the Debian version (and have not replaced > amavisd-new with the original amavisd) then you would edit the files > in /etc/amavis/conf.d/ to configure amavisd-new. I assume you have been > doing this, is this correct? Yes, I'm using /etc/amavis/conf.d/ files, there is no amavisd.conf at all. Regards, Frank ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
