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 permanent error not cause a bounce
> as mandated by the RFC?
>
> > Config parameters from the old config:
> > MX1-OLD:~# postconf -n | grep lmtp
> > lmtp_sasl_auth_enable = yes
> > lmtp_sasl_password_maps = hash:/etc/postfix/lmtp_passwd
> > lmtp_sasl_security_options =
> > mailbox_transport = lmtp:lmtp.mx-domain.tld:2003
This is not a valid LMTP nexthop. From lmtp(8)
LMTP destinations have the following form:
unix:pathname
Connect to the local UNIX-domain server that is
bound to the specified pathname. If the process
runs chrooted, an absolute pathname is interpreted
relative to the Postfix queue directory.
inet:hostname
inet:hostname:port
inet:[address]
inet:[address]:port
Connect to the specified TCP port on the specified
local or remote host. If no port is specified, con-
nect to the port defined as lmtp in services(4).
If no such service is found, the lmtp_tcp_port con-
figuration parameter (default value of 24) will be
used. An IPv6 address must be formatted as
[ipv6:address].
Try:
mailbox_transport = lmtp:inet:lmtp.mx-domain.tld:2003
The 2.2.12 documentation says:
The LMTP client connects to the destination specified in the message
delivery request. The destination, usually specified in the Postfix
transport(5) table, has the form:
unix:pathname
Connect to the local UNIX-domain server that is bound to the
specified pathname. If the process runs chrooted, an absolute
pathname is interpreted relative to the changed root directory.
inet:host, inet:host:port (symbolic host)
inet:[addr], inet:[addr]:port (numeric host)
Connect to the specified IPV4 TCP port on the specified local or
remote host. If no port is specified, connect to the port
defined as lmtp in services(4). If no such service is found,
the lmtp_tcp_port configuration parameter (default value of 24)
will be used.
The LMTP client does not perform MX (mail exchanger) lookups
since those are defined only for mail delivery via SMTP.
If neither unix: nor inet: are specified, inet: is assumed.
So it looks like the "inet:" default went away when LMTP was merged with
SMTP in 2.3.
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majord...@postfix.org?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
