Hi, > You've just described it. Can you ask a more specific question? > Each Postfix instance behaves like a full-blown independent MTA, > they just happen to run on the same machine. You can forward > traffic between them via SMTP. > > For any given IP address and TCP port, at most one Postfix instance can > listen on that IP and port, and if the port is used with a wildcard > listener, then that generally precludes using it with specific IPs. > > > I have an existing system that uses amavisd, clamav and spamassassin > > using "content_filter = smtp-amavis:[127.0.0.1]:10024". Just to be > > sure, this (along with my postscreen and smtpd_recipient_restrictions) > > goes in postfix-in, correct? > > With multiple instances one you don't actually need a "content_filter", > you can instead arrange for the transport table and/or local_transport, > virtual_transport, relay_transport, default_transport (whichever are > applicable) to hand mail off to the filter port. But you can continue > to use content_filter if you like.
I'd like to try and do this without using content_filter but I'm having a problem. Mail appears to be completely ignoring the amavisd proxy despite configuring default_transport to use 10025. # netstat -ntap|grep 1002 tcp 0 0 127.0.0.1:10025 0.0.0.0:* LISTEN 598039/amavisd (mas tcp 0 0 127.0.0.1:10026 0.0.0.0:* LISTEN 597710/master # postmulti -l - - y /etc/postfix postfix-out mta y /etc/postfix-out postfix-114 mta y /etc/postfix-114 postfix-117 mta y /etc/postfix-117 postfix-114 default_transport = smtp:[127.0.0.1]:10025 relay_transport = $default_transport virtual_transport = $default_transport postfix-117 default_transport = smtp:[127.0.0.1]:10025 relay_transport = $default_transport virtual_transport = $default_transport In postfix-out: # Replace default "smtp inet" entry with one listening on port 10026. 127.0.0.1:10026 inet n - n - - smtpd What am I missing? I don't know what more info I can provide to troubleshoot this.
