Re: two postfix instances

On Monday 30 May 2005 7:11 pm, D. Walsh wrote:
> > On Mon, May 30, 2005 7:49 am, D. Walsh said:
> >> How can I share a single content filter between 2 postfix
> >> instances???

Simple :-) I have this exact setup on my network (amavisd-new + 2 x=20
postfix).

The first port pair for the content scanner is 10024/10025 and the second=20
instance uses 10026/10027

The following is good for the first (1) instance of Postfix.

> 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
=2E..
[snip]

You need to specify the content filter in main.cf for the 1st instance.
=3D=3D=3D=3D=3D=3D=3D=3D/etc/postfix/main.cf (1) =3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
content_filter =3D smtp-amavis:[127.0.0.1]:10024
=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


My second instance is running on another machine but the following is the o=
nly=20
change to master.cf I need. If you're running the 2nd instance on the same=
=20
machine (!!??) then you probably should specify the appropriate interface=20
too.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D/etc/postfix/master.cf (2)=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
10027 inet n - n - - smtpd
-o content_filter=3D
-o local_recipient_maps=3D
=2E..
=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

You need to specify the content filter for the second instance of postfix a=
lso=20
as before.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D/etc/postfix/main.cf (2) =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
content_filter =3D smtp-amavis:[192.168.0.3]:10026
=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

Replace the 192.168.0.3 address as necessary for your installation.

> OK so how do I get both instances to use the same amavisd-new if I
> can't define it in both?
>
> I've gone over the amavisd-new stuff and it doesn't seem to work with
> multiple assignment of port pairs so what;s the solution.
>
> -- Dale

=46rom my /etc/amavisd.conf
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D/etc/amavisd.conf=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
# To make it possible for several hosts to share one content checking daemo=
n,
# the IP address and/or the port number in $forward_method and $notify_meth=
od
# may be spacified as an asterisk. An asterisk in the colon-separated
# second field (host) will be replaced by the SMTP client peer address,
# An asterisk in the third field (tcp port) will be replaced by the incoming
# SMTP/LMTP session port number plus one. This obsoletes the previously used
# less flexible configuration parameter $relayhost_is_client. An example:
# $forward_method =3D 'smtp:*:*'; $notify_method =3D 'smtp:*:10587';
$forward_method =3D 'smtp:*:*';
$notify_method =3D $forward_method;

=2E..

# SMTP SERVER (INPUT) PROTOCOL SETTINGS (e.g. with Postfix, Exim v4, ...)
# (used when MTA is configured to pass mail to amavisd via SMTP or LMTP)
#$inet_socket_port =3D 10024; # accept SMTP on this local TCP port
# (default is undef, i.e. disabled)
# multiple ports may be provided: $inet_socket_port =3D [10024, 10026, 1002=
8];
$inet_socket_port =3D [10024, 10026];
=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

I think that's all there is to it.

Hope this helps.