At 04:53 PM 11/5/2007, Michael Hallager wrote: > > You need to check your logs to see why the message is marked as > > spam. Running amavisd at log level 2 or higher ($log_level = 2; in > > amavisd.conf) will likely give you enough information to see why the > > message is rejected. Here's some wild guesses you can track down: > >Will try. > > > - SpamAssassin Auto WhiteList "AWL" or bayes features can > > automatically learn mail as spam. > > You can try temporarily disabling AWL and bayes by adding the > > following to your spamassassin /etc/mail/spamassassin/local.cf > > use_bayes 0 > > use_auto_whitelist 0 > > see http://wiki.apache.org/spamassassin/BasicConfiguration > >Where does it store this information? I think if I can delete the state and >start again, this will fix the problem whereas setting it not to use the >above will degrade the performance.
If you didn't set SA to use *SQL for these tables, they are stored in the SA global config directory, usually /etc/mail/spamassassin, as auto-whitelist* and bayes*. Stop amavisd-new and anything else that uses SpamAssassin (such as if you configured spamd to run for some reason), and then just remove those files. But if you don't check the logs to see if this is really the problem, you're just shooting in the dark. -- Noel Jones ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
