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

2016-08-28 Thread ellie timoney via Info-cyrus
The "Bad IP(LOCAL|REMOTE)PORT value" log entries come from sasl, not from lmtpd itself -- https://git.io/v6jvs, lines 1171 and 1212. The corresponding calls to sasl_setprop seem to come from lines 1088-9 of lmtpengine.c: https://git.io/v6jJf The two IP address parameters in this case are the loca

Re: cyradm "info" behavior after cyrus-imapd-2.3.16 -> 2.5.9 upgrade

2016-08-28 Thread Andy Dorman via Info-cyrus
On 08/26/2016 09:47 AM, Tod A. Sandman via Info-cyrus wrote: I noticed after upgrading from cyrus-imapd-2.3.16 to cyrus-imapd-2.5.9 that the "info" cyradm command no longer works: it prints out nothing. Furhermore, after issuing the info command, no other commands print anything either. For i

Re: how to deal with mail retention/archival.

2016-08-28 Thread André Felipe Machado via Info-cyrus
Hello 1 - http://www.enkive.org ? 2 - expunge delay , but sent msg on client not copying to a sent folder? 3 - postfix always bcc to a second Cyrus system? Regards André Felipe Em 27 de agosto de 2016 13:29:14 BRT, Bron Gondwana via Info-cyrus escreveu: > > > >On Sat, 27 Aug 2016, at 02:13, Sh

Re: cyradm "info" behavior after cyrus-imapd-2.3.16 -> 2.5.9 upgrade

2016-08-28 Thread Ken Murchison via Info-cyrus
Are you sure that you are using the cyradm from 2.5.9? IIRC, older cyradm doesn't like the responses sent by 2.5.x servers. On 08/26/2016 10:47 AM, Tod A. Sandman via Info-cyrus wrote: I noticed after upgrading from cyrus-imapd-2.3.16 to cyrus-imapd-2.5.9 that the "info" cyradm command no lo