OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
lmtp port in 2.1.5 vs 2.3.8

From: Rudy Gevaert (Rudy.GevaertUGent.be)
Date: Tue Aug 05 2008 - 06:43:27 CDT


Hi,

Previously we were running postfix 2.1.5 (Debian Sarge) and now have
upgraded to 2.3.8 (Etch).

We have several lmtp transports in master.cf:

mail1 unix - - n - - lmtp
mail2 unix - - n - - lmtp
mail3 unix - - n - - lmtp

We used an ldap directory to route to the correct backend:
umTransport: mail1:mail1.ugent.be

In postfix 2.1.5 the destination port of our lmtp connections was *by
default* 2003. Because we had the following entry in /etc/services:
lmtp 2003/tcp

When I did the upgrade to 2.3.8 I noticed that was not the case anymore.
  It connected to an other port (I can't remember what anymore).

I tried changing lmtp_tcp_port to 2003 but that didn't help. In the end
I changed the result attribute of my ldap lookup to add the port number
to the transport:
result_format = %s:2003

I was wondering why this was changed, or did I miss something?

Thanks in advance,
--
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Rudy Gevaert Rudy.GevaertUGent.be tel:+32 9 264 4734
Directie ICT, afd. Infrastructuur ICT Department, Infrastructure office
Groep Systemen Systems group
Universiteit Gent Ghent University
Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --