On 2018-04-23 (14:13 MDT), Viktor Dukhovni <postfix-us...@dukhovni.org> wrote: > > On Apr 23, 2018, at 3:50 PM, @lbutlr <krem...@kreme.com> wrote: >> <http://www.postfix.org/postconf.5.html#inet_interfaces> >> When inet_interfaces specifies just one IPv4 and/or IPv6 address that is not >> a loopback address, the Postfix SMTP client will use this address as the IP >> source address for outbound mail. Support for IPv6 is available in Postfix >> version 2.2 and later. > > The conditions are: > > * Exactly one address (of the appropriate address family) > * That address is not a loopback address
That is not how I read it, I read it as one IPv4 and/or one IPv6 address (that is not a loopback which you can certainly have also because obviously you are almost certainly doing to have a loopback). > The text could be read as: > > * Exactly one non-loopback address (of the appropriate address family) If that is what is intended, that would be much clearer, yes. > but that's not what is implemented. 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. Sadly, they cannot do webforms either as their form appears to only work in Chrome, so I'm not super impressed with them today. Thanks for the explanation, but I do think the documentation needs to be clearer.
