Re: two postfix instances

On May 30, 2005, at 02:25 AM, Magnus B=E4ck wrote:

> On Mon, May 30, 2005 7:49 am, D. Walsh said:
>
>
>> How can I share a single content filter between 2 postfix =20
>> instances???
>>
>
> No problem. You'll just have to make sure amavisd-new reinjects the
> message to the same instance from which the message came. I think
> amavisd-new is capable of this, but I don't remember exactly how.


I can't have the following defined in both instances, it wont start =20
because ofthe interface/port issue.

#
# =20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=20
=3D=3D
# AMAVIS - CLAMAV
# =20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=20
=3D=3D
#
smtp-amavis unix - - y - 2 smtp
-o smtp_data_done_timeout=3D1200
-o smtp_send_xforward_command=3Dyes
-o disable_dns_lookups=3Dyes
127.0.0.1:10025 inet n - n - - smtpd
-o content_filter=3D
-o local_recipient_maps=3D
-o relay_recipient_maps=3D
-o smtpd_restriction_classes=3D
-o smtpd_client_restrictions=3D
-o smtpd_helo_restrictions=3D
-o smtpd_sender_restrictions=3D
-o smtpd_recipient_restrictions=3Dpermit_mynetworks,r eject
-o mynetworks=3D127.0.0.0/8
-o strict_rfc821_envelopes=3Dyes
-o smtpd_error_sleep_time=3D0
-o smtpd_soft_error_limit=3D1001
-o smtpd_hard_error_limit=3D1000
-o receive_override_options=3Dno_header_body_checks

>
>> The contrent filter I am refering to is amavisd-new.
>>
>> I'm also noticing I am unable to use locathost in both instances as
>> it fails to start citing:
>>
>> May 30 01:24:26 dellc postfix-secondary/master[21289]: fatal: bind
>> 127.0.0.1 port 25: Address already in use
>>
>
> Yes, obviously you can't have two Postfix instances listening on =20
> the same
> port on the same interface.
>
>
>> It also seems that I cannot define amavisd-new in both so I was
>> wondering how to achieve this.
>>
>
> What does "define amavisd-new" mean? A master.cf entry? Of course =20
> you can
> have amavisd-new services in both instances. What makes you think
> otherwise?

Yes a main/master entry.

>
>> Because smtp-amavis is defined in the first postfix instance, can I
>> call it from the second without defining it or defining in the second
>> postfix instance will allow me to use it:
>>
>> /etc/postfixalt/main.cf:
>> content_filter=3Dsmtp-amavis:[127.0.0.1]:10024
>>
>
> Two Postfix instances do not share a single master.cf, so if you =20
> want to
> refer to a transport named "smtp-amavis" it must exist in the =20
> instance in
> question.

OK so how do I get both instances to use the same amavisd-new if I =20
can't define it in both?

I've gone over the amavisd-new stuff and it doesn't seem to work with =20=

multiple assignment of port pairs so what;s the solution.

>
>> Please don't reference any man page stuff unless you are going to
>> send me your computer so I can see what you're talking about.
>>
>> My OS vendor screws with the man pages so I don't have what you do so
>> please be specific and detailed when you respond.
>>
>
> The Postfix man pages are available from the Postfix web site.
>
> --=20
> Magnus B=E4ck
> magnus@dsek.lth.se

-- Dale=