Questions before upgrading vom 2.3 to 2.4

[Sebastian Hagedorn]

Hi,






# imtest -u xxx -a xxx localhost

C: A01 AUTHENTICATE DIGEST-MD5
S: + <snip>
Please enter your password:
C: <snip>
S: A01 NO authorization failure
Authentication failed. generic failure
Security strength factor: 128

In the logfile I can see that it's working:

Jan  5 14:39:58 centos-hg imap[19662]: accepted connection
Jan  5 14:39:58 centos-hg imap[19662]: wild: 'imap*'   service: 'imap'
Jan  5 14:39:58 centos-hg imap[19662]: pat 0:'imap*'


Is this intentional or not to be avoided, or should I file a bug report?



 delprune       cmd="cyr_expire -E 3 -X 3 -D 3" at=0400







Thanks, Sebastian
--
    .:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:.
                .:.Regionales Rechenzentrum (RRZK).:.
.:.Universität zu Köln / Cologne University - ✆ +49-221-478-5587.:.

we're currently running a rather outdated configuration, with Cyrus 2.3.14 and RHEL 3 i386 on hardware that's almost 7 years old. I'm planning an upgrade to 2.4 with RHEL 5 x86_64 and I have a umber of questions regarding new features that I played around with using 2.4.13. I've searched the archives and found some answers, but not all. • this is more an observation: when you use the user_deny.db feature, the reason isn't given back to the user when IMAP is used, e.g.: S: * OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE STARTTLS LOGINDISABLED AUTH=DIGEST-MD5 AUTH=CRAM-MD5 SASL-IR] cyrus.rrz.uni-koeln.de Cyrus IMAP v2.4.13-Invoca-RPM-2.4.13-1 server ready Jan 5 14:39:58 centos-hg imap[19662]: user 'xxx' denied access to service 'imap' Jan 5 14:39:58 centos-hg imap[19662]: badlogin: xxx.rrz.uni-koeln.de [134.95.x.x] DIGEST-MD5 [SASL(-14): authorization failure: user 'xxx' is denied access to service 'imap'] • how do the 'expunge_days' option in imapd.conf and the -X flag to cyr_expire play together? Currently, we're using this cyrus.conf entry: I'm not clear if we should use 'expunge_days: 3' from now on or if it doesn't matter? • I'm not sure if we'll want to use metapartitions, but I'm curious what happens when you change that value on an existing installation? Would we have to move the relevant files ourselves, or is there an automated procedure in place? BTW, the manpage for 2.4.13 still lists "expunge" as allowed value for metapartition_files, but cyrus.expunge doesn't exist anymore ... • tcp_keepalive: we've always had problems with POP and IMAP processes that got stuck when a connection was dropped in the "right" way. It's gotten better over the years, but it still happens with 2.3.14. I'm thinking that tcp_keepalive might get rid of this problem for good. Thoughts? Is there a downside I'm not seeing?

p7si0geftJuiY.p7s
Description: S/MIME cryptographic signature

----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/