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 local and remote IP of the socket connection -- so,
lmtpd's IP (local), and postfix's (remote).

It's a shame sasl doesn't log the bad values -- it might have saved some
time to know what they were.  On a hunch though, do you have reverse DNS
set up for the IPs postfix and cyrus are using?  Is DNS resolution
working correctly on the cyrus server?

I wonder if you also upgraded sasl when you upgraded cyrus?  If so, from
which version to which?  (Maybe this condition always existed but some
older version of sasl didn't bother reporting it.)

Cheers,

ellie

On Fri, Aug 26, 2016, at 11:02 PM, Andy Dorman via Info-cyrus wrote:
> 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.
> >>
> >> lmtpcmd="lmtpd" listen="*:lmtp" prefork=10 maxchild=20
> >>
> >> I have also tried replacing the wildcard host with listen="lmtp" and
> >> still receive "Bad IPPOST 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
> >
> 
> 
> 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

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 instance:

  cyrus@cyrus2a:/var/imap/sync> cyradm --user mailadmin `hostname`
  cyrus2a.mail.rice.edu> lm user/lamemm7
  user/lamemm7 (\HasChildren)
  cyrus2a.mail.rice.edu> lam user/lamemm7
  mailadmin lrswipkxtecda
  lamemm7 lrswipkxtecda
  cyrus2a.mail.rice.edu> info user/lamemm7
  cyrus2a.mail.rice.edu> lam user/lamemm7
  cyrus2a.mail.rice.edu> lm user/lamemm7

Anyone else experiencing this?


Tod Sandman

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



Tod, we just finished upgrading several debian servers from 2.4.18 to 
2.5.9 and do not see the behavior you are describing.


I will note that debian dependencies did not seem to catch that we 
needed to upgrade cyrus-admin at the same time as cyrus-imap, so maybe 
you are still using cyrus-admin 2.3.x?


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

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, Shawn Bakhtiar via Info-cyrus wrote:
>>
>>> On Aug 26, 2016, at 8:35 AM, Giuseppe Ravasio (LU) via Info-cyrus
>>> cy...@lists.andrew.cmu.edu> wrote:
>>>
>>> I saw that someone proposed to make a sort of abuse of delayed
>>> expunge,
>>>  but I think that in order to comply with regulatory retention
>>>  should be
>>>  better considering some specific software.
>>>
>>
>> I don't see how using delayed expunge would really be consider abuse,
>> the documentation makes mention of its use for this very reason.
>
>You will hit performance issues. All expunged messages need to be
>scanned over at every select and refresh.
>
>> "In any case, the time between a message arriving and being deleted
>> may not be sufficient to ensure the message is replicated, included
>in
>> the next backup cycle, and generally available for recovery or
>> compliance with the regulatory environment."
>> --src  https://cyrusimap.org/imap/features/delayed-expunge.html
>
>If you are replicating to a system that's backing up, then you need
>delayed delete to ensure everything gets replicated.
>
>The backup system that's in development uses the sync protocol to feed
>the data from Cyrus into the backups.
>
>> We use rsync to make a duplicate of the email spool to a file server
>> at regular intervals, which eventually makes its way to tape.
>Although
>> we don't have regulatory requirements I've had to do a few recoveries
>> and have done so without problem.
>>
>> in our case we have cyr_expire set to 3 days (I believe the default
>> config), which provides more than enough time to in case a backup
>> fails for some reason or another.
>>
>>
>>> For example:
>>> http://www.mailpiler.org (Fully Free Software)
>>> https://www.mailarchiva.com (the old version is opensource but the
>>>  latest is closed)
>>>
>>> The specific software will be much better for searching the archive.
>>>  Finding something in the delayed_expunge folders after many years
>of
>>>  archive will absolutely be a nightmare!
>>>
>>
>>
>> Of course these tools offer features but that all comes at a price.
>>
>>
>>>
>>
>>
>>> Giuseppe
>>>
>>>
>>>  On 08/26/2016 03:09 PM, Alvin Starr via Info-cyrus wrote:
>>>
 A company I am working with is facing issues of regulatorymail
 retention.

  Some searching has yielded little useful results other than
  putting a
  system in front to store all incoming messages.

  What are others doing for mail archival?

  An ideal solution would let the users carry on using current use
  patterns and not impose extra restrictions.

  --
  Alvin Starr   ||   voice: (905)513-7688
  Netvel Inc.   ||   Cell:  (416)806-0133
 al...@netvel.net ||



  
  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
>>
>> 
>> 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
>
>--
>  Bron Gondwana
>  br...@fastmail.fm
>
>
>
>
>
>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

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
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

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 longer works: it prints out nothing.  Furhermore, 
after issuing the info command, no other commands print anything either.  For instance:

   cyrus@cyrus2a:/var/imap/sync> cyradm --user mailadmin `hostname`
   cyrus2a.mail.rice.edu> lm user/lamemm7
   user/lamemm7 (\HasChildren)
   cyrus2a.mail.rice.edu> lam user/lamemm7
   mailadmin lrswipkxtecda
   lamemm7 lrswipkxtecda
   cyrus2a.mail.rice.edu> info user/lamemm7
   cyrus2a.mail.rice.edu> lam user/lamemm7
   cyrus2a.mail.rice.edu> lm user/lamemm7

Anyone else experiencing this?


Tod Sandman

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


--
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University


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