lmtp "Bad IPLOCALPORT value" and "Bad IPREMOTEPORT value" after upgrade 2.4.18 to 2.5.9

[Andy Dorman]

Thanks for checking and good question, yes.

lmtp      2003/tcp

I doubt it would have been working fine for all these years with the 2.4 
versions without that. ;-)

And let me be clear...it still works fine.  We just have these annoying 
2 log messages before auth happens (see below).

It looks like lmtp is reporting the IPLOCALPORT and IPREMOTEPORT value 
problems before auth is done, but once auth finishes lmtp is happy.

2016-08-25T10:27:40.130890-05:00 yorick cyrus/lmtp[5695]: Bad 
IPLOCALPORT value
2016-08-25T10:27:40.130915-05:00 yorick cyrus/lmtp[5695]: Bad 
IPREMOTEPORT value
2016-08-25T10:27:40.152889-05:00 yorick cyrus/lmtp[5695]: login: 
ophelia.ironicdesign.com [192.168.0.9] cyrus PLAIN User logged in

I looked at the lmtpengine.c source on github and did not see an obvious 
source for this particular log output...but I am not a C programmer and 
could be completely missing what is going on here.

Andy Dorman

On 08/25/2016 06:19 PM, ellie timoney via Info-cyrus wrote:
> Do you have "lmtp" defined in /etc/services?
>
> On Thu, Aug 25, 2016, at 08:44 AM, Andy Dorman via Info-cyrus wrote:
>> We have a cluster of servers that provide external email security
>> filtering and then postfix delivers the safe email via lmtp to mailboxes
>> on the various servers in the cluster (using SASLauth of course).
>>
>> I just updated our dev server to 2.5.9 and while email delivery seems to
>> be working fine, now we are seeing these messages every time postfix
>> delivers email to the upgraded server:
>>
>> cyrus/lmtp[8140]: Bad IPLOCALPORT value
>> cyrus/lmtp[8140]: Bad IPREMOTEPORT value
>>
>> Our cyrus.conf config for lmtp looked like this at the time of the
>> change.
>>
>> lmtp            cmd="lmtpd" listen="*:lmtp" prefork=10 maxchild=20
>>
>> I have also tried replacing the wildcard host with listen="lmtp" and
>> still receive "Bad IPxxxxPOST value".
>>
>> So this almost seems like postfix is not communicating the lmtp
>> correctly and Cyrus is reporting it but then goes on to handle it?
>>
>> FWIW, our postfix does an LDAP lookup to fetch the hostname to deliver
>> the email within the cluster.  The hostname is plugged into this
>>
>> result_filter = lmtp:inet:%s:lmtp
>>
>> So is Cyrus now looking for something different from postfix?  ie,
>> should I be talking to the Postfix folks instead of bothering everyone
>> here? ;-)
>>
>> Sincere regards,
>>
>> --
>> Andy Dorman
>> Ironic Design, Inc.
>> AnteSpam.com
>>
>> ----
>> Cyrus Home Page: http://www.cyrusimap.org/
>> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
>> To Unsubscribe:
>> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
>