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 yori
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
ious 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 IPLO
, 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.
lmtpcmd="lmtpd" list
he the rellevant lines in the imapd.conf are:
> allowplaintext: yes
> sasl_pwcheck_method: saslauthd
> sasl_mech_list: PLAIN
> sasl_minimum_layer: 0
>
> in the auth.log i find:
> Sep 25 00:13:48 brainserv perl: No worthy mechs found
> Sep 25 00:13:59 brainserv cyrus/imapd[610]: Bad I
ok. More issues! - what is causing this and how do I trouble shoot it?
Everything -is- working fine..but these messages are tossed on the console
of my sun box anytime anything related to cyrus happens:
sun1 console login: Sep 21 20:06:38 sun1 pop3d[9053]: Bad IPLOCALPORT value
Sep 21 20:06:38
