> > Mail appears to be completely ignoring the amavisd proxy despite
> > configuring default_transport to use 10025.
>
> The default_transport is a last-resort, it is preƫmpted both by the
> transport table, and the address-class-specific transports.  It handles
> "other people's domains".  Mail for your own domains (local, virtual
> mailbox, relay, ...) uses local_transport, virtual_transport or
> relay_transport.  And all those are secondary to any transport(5)
> table you have configured.

I still don't understand the link between postfix and amavis. No mail
is delivered locally, except for system messages, so I don't need a
local_transport, right?

postfix-117:
mydestination =
local_recipient_maps =
local_transport = error:5.1.1 Mailbox unavailable
default_transport = smtp:[127.0.0.1]:10025
relay_transport = $default_transport
virtual_transport = $default_transport
transport_maps = ${indexed}transport
local_transport = error:5.1.1 Mailbox unavailable
transport_maps = ${indexed}transport
relay_domains = $mydestination, $transport_maps

/etc/postfix-117/transport:
mydomain.org                      smtp-amavis:[127.0.0.1]:10025

master.cf:
smtp-amavis unix    -       -       n       -       -   smtp
    -o smtp_data_done_timeout=1200
    -o smtp_send_xforward_command=yes

I'm really not sure what to do next. I've previously used
virtual_alias_maps with mydestination, but not virtual_transport. I'm
just unsure how all the pieces fit together. This is all based on
following the multi-instance doc as explicitly as possible, but I
think it leaves a lot to be desired in terms of how to produce a
functional system.

> > # 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
>
> The downstream amavis or Postfix is not configured correctly and is
> dropping connections.   The reason is in your logs.

This also generates the following amavis error:
Nov  8 00:01:57 xavier amavis[812131]: (!)DENIED ACCESS from IP
209.216.11.117, policy bank ''

I've read that enabling smtp_bind_address=127.0.0.1 is necessary, but
that just creates a mail loop.

Reply via email to