That's what I'm talking about. Thanks alot. I'll try this on one MX and see how things go for a week or two.
Cheers, Gary V wrote: > Gordon wrote: > > >>That makes sense. The primary MX gets much more traffic than then backup >>MX, but I was hoping that Amavisd-new would not bother running spam >>tests on something clearly generated by itself. > > > If you are running Postfix, you can bypass amavisd-new for mail that > is created by the machine itself, but this also means any locally > generated mail will bypass amavisd-new, so it may not be appropriate > in all cases. In master.cf, add '-o content_filter=' to the pickup > service: > > pickup fifo n - - 60 1 pickup > -o content_filter= > > Alternately, you can remove this from main.cf: > content_filter = smtp-amavis:[127.0.0.1]:10024 > and only include it in master.cf for the desired services, for example: > > smtp inet n - - - - smtpd > -o content_filter=smtp-amavis:[127.0.0.1]:10024 > > Or you could use a policy bank instead of bypassing amavisd-new > altogether if you like: > > pickup fifo n - - 60 1 pickup > -o content_filter=smtp-amavis:[127.0.0.1]:10026 > > then in amavisd.conf, something like: > > $inet_socket_port = [10024,10026]; # change this default > > $interface_policy{'10026'} = 'BYPASSSPAM'; > > $policy_bank{'BYPASSSPAM'} = { > bypass_spam_checks_maps => [1], > final_spam_destiny => D_PASS, > }; > > Gary V _______________________________________________ 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/