postfix and amavis reg.

[ANANT S ATHAVALE]

Dear Mark,

Thank you very much.  I also went through Policy Bank related  
documents and understood the concept.  Thank you very much.

Regards,
Anant.


----- Message from Mark.Martinec+amavis at ijs.si ---------
     Date: Tue, 4 Sep 2012 18:08:04 +0200
     From: Mark Martinec <Mark.Martinec+amavis at ijs.si>
  Subject: Re: postfix and amavis reg.
       To: amavis-users at amavis.org


> Anant,
>
>> Right now, I have only one postfix instance connecting with Amavis for
>> virus scanning (ClamAV).  Situation now demands me to run one more
>> instance of Postfix on the same server.
>>
>> Should I start one more instances of Amavis alone?
>
> No need to.
>
>> Should I start one more instances of Amavis and Clamd?
>
> No, keep just one clamd.
>
>> Should I start one more instances of Amavis, Clamd and SpamAssassin?
>
> What do you mean by instances of SpamAssassin?
> There is no spamd, so SpamAssassin is running within each
> amavisd child process.
>
>> Or, I can use the same instance of Amavis/Clamd/SpamAssasin.
>
> You probably want amavisd to feed passed mail back to the same
> MTA where it came from, so it would make sense to use two
> amavisd port numbers, one for each MTA. To give you some extra
> flexibility in allowing different settings to apply to each
> submission port use policy banks. Something like this:
>
> $inet_socket_port = [10024, 10026];
>
> $interface_policy{'10024'} = 'MTA1';
> $interface_policy{'10026'} = 'MTA2';
>
> $policy_bank{'MTA1'} = {
>   # whatever config overrides are needed for MTA1
>   forward_method => 'smtp:[127.0.0.1]:10025',
>   notify_method  => 'smtp:[127.0.0.1]:10025',
> };
>
> $policy_bank{'MTA2'} = {
>   # whatever config overrides are needed for MTA1
>   forward_method => 'smtp:[127.0.0.1]:10027',
>   notify_method  => 'smtp:[127.0.0.1]:10027',
> };
>
>
> Mark
>


----- End message from Mark.Martinec+amavis at ijs.si -----



Regards,

Anant Athavale.

------------------------------------------------------------------------------
Confidentiality Notice: This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.
------------------------------------------------------------------------------