> On Apr 23, 2018, at 5:09 PM, @lbutlr <[email protected]> wrote:
>
>> If you also list "127.0.0.1" the bind address will not be set. This makes
>> sense, because either address may be needed for some subset of the
>> connections. The text could be more clear, but bottom line you need to set
>> smtp_bind_address explicitly, possibly per-transport, if some transports
>> deliver to localhost.
>
> OK, so I will simply write-off synology as a company that cannot do email
> properly. I'm not going to jump through a bunch of hoops just to try to
> please their broken server.
I don't think that splitting off traffic destined for 127.0.0.1 onto a separate
transport is much work, in fact generally a good idea anyway, see for example
the "scan" transport in:
http://www.postfix.org/FILTER_README.html#advanced_filter
With separate transports, one can have "-o smtp_bind_address=127.0.0.1" and the
stock "smtp" and "relay" transports can have "-o smtp_bind_address=192.0.2.1"
(or whatever you have for an external address). Seems pretty light-weight to
me, but you call of course for your systems...
--
Viktor.
