Hi,

I'm still working on trying to get my multi-instance postfix
installation working with amavis.

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

I've experimented with transport_maps like this:
mycompany.org                      smtp-amavis:[127.0.0.1]:10025

smtp-amavis unix    -       -       n       -       -   smtp
    -o smtp_data_done_timeout=1200
    -o smtp_send_xforward_command=yes

but mail just sits in the queue:

# mailq -C /etc/postfix-117
-Queue ID-  --Size-- ----Arrival Time---- -Sender/Recipient-------
D9DE7200B23F3    2516 Tue Nov  3 20:34:30  mysqlstud...@gmail.com
(lost connection with 127.0.0.1[127.0.0.1] while receiving the initial
server greeting)
                                         a...@mycompany.org

What am I missing? I don't know what more info I can provide to
troubleshoot this.

Reply via email to