Gary wrote: > Anne wrote:
>> I've disabled my spam checking: >> # Here is a QUICK WAY to completely DISABLE some sections of code >> # that WE DO NOT WANT (it won't even be compiled-in). >> # For more refined controls leave the following two lines commented out, >> # and see further down what these two lookup lists really mean. >> # >> # @bypass_virus_checks_acl = qw( . ); # uncomment to DISABLE anti-virus >> code >> @bypass_spam_checks_acl = qw( . ); # uncomment to DISABLE anti-spam code >> but it still starts the spam checking code: >> Oct 12 14:51:09 banshee amavisd[8827]: SpamControl: initializing >> Mail::SpamAssassin >> Oct 12 14:51:13 banshee amavisd[8827]: SpamControl: done >> and it still tags messages: >> Why? What can I do to stop it? > Look further down in your amavisd.conf file to see if this was > overwritten by another assignment (possibly in a policy bank?): > @bypass_spam_checks* > grep bypass_spam /path/to/amavisd.conf > I don't believe this assignment will prevent newer versions of > amavisd-new from loading the spamassassin modules however. > It will continue to bypass_spam_checks. Provided you are using a 2.0 or greater version, replace it with: @bypass_spam_checks_maps = (1); (and still make sure it is not assigned later in amavisd.conf) This does appear to prevent spamassassin from loading in newer versions. Gary V ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ 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/
