content-filter with Postfix

Robert Moskowitz rgm at htt-consult.com
Wed Mar 8 21:25:22 CET 2017



On 03/08/2017 02:45 PM, DaLiV wrote:
> All is simple:
> when you pass to filter ALL mail - then can use main.cf directive ...
> but when You want to make diffirent access to diffirent services /IP 
> or Port based/ then surelly more advisable to use master.cf, where 
> behavior is defined for each subservice ...

And which services would one NOT pass to amavis?  So what you might do 
is have the global rule and for a couple services that break going to 
amavis, have them use content_filter=

Like maybe amavis itself?  :)

>
> Robert Moskowitz wrote:
>> I am on Centos 7.
>>
>> I am reading a lot of different places, including:
>>
>> /usr/share/doc/amavisd-new-2.10.1/README_FILES/README.postfix
>>
>> that seem to imply that main.cf should have
>>
>> content_filter=amavisfeed:[127.0.0.1]:10024
>>
>> instead of sprinkling it all over master.cf as a -o line.
>>
>> Does anyone have any knowledge on this?  if in master.cf, which 
>> services do NOT use amavis?
>>
>> thank you
>>
>>
>



More information about the amavis-users mailing list