Victor Duchovni:
> So it looks like the "inet:" default went away when LMTP was merged with
> SMTP in 2.3.
The code attempts to be backwards compatible:
/*
* With LMTP we have direct-to-host delivery only. The destination may
* have multiple IP addresses.
*/
if (state->misc
On Tue, Apr 07, 2009 at 05:17:44PM +0200, Bastian Blank wrote:
> On Tue, Apr 07, 2009 at 04:56:52PM +0200, Martin Zobel-Helas wrote:
> > while trying to upgrade from Postfix 2.1.5 to a newer version, i
> > experience problems with LMTP bounce handling.
>
> Please define problems. Why should a per
On Tue, Apr 07, 2009 at 04:56:52PM +0200, Martin Zobel-Helas wrote:
> while trying to upgrade from Postfix 2.1.5 to a newer version, i
> experience problems with LMTP bounce handling.
Please define problems. Why should a permanent error not cause a bounce
as mandated by the RFC?
> Config paramete
Hi,
while trying to upgrade from Postfix 2.1.5 to a newer version, i
experience problems with LMTP bounce handling.
old postfix version:
postfix/lmtp[13549]: E379B1C07E: to=,
relay=lmtp.mx-domain.tld[XXX.XXX.XXX.XXX], delay=6, status=deferred
(Authentication failed: SASL authentication failed;
s
