Arch Linux User Repository

I have uploaded cyrus-imapd-ldap, which adds LDAP support to this package. This way is more modular, but merging it in this package may be more simple (no need to install two packages).

Hi, I am trying to pack Kolab for Arch, and it uses cyrus-imapd as its LDA. However, I need LDAP support to make it work. Would you consider adding it to this package? It can be done just by adding libldap as a dependency and passing "--with-ldap=/usr" to the configure script. Thanks

Ignore my comment regarding /etc/sasldb2 -- this *is* used by cyrus-imapd. I always use cyrus -> saslauthd -> PAM for authentication, so don't actually use sasldb2. I would recommend avoiding this and just go with the PAM solution.

The only file in /usr/share/doc/cyrus-imapd is a README which states, in part ------------------- For the real README file, please see doc/readme.html. * To install the software, please read doc/install.html (but please read doc/readme.html first!). * To see the changes since previous versions, check doc/changes.html, and if upgrading look at doc/install-upgrade.html as well. ------------------- Any reason why the docs aren't included with this package? In nothing else, there should be an auxilliary doc package to go with this one (although cyrus documentation is minimal, and takes up hardly any space.

> However /etc/sasldb2 is still in berkeley-hash format I'm guessing this file is created by cyrus-sasl, and not cyrus?

I checked some of my db files like /usr/lib/cyrus/bin/cyr_dbtool /var/imap/mailboxes.db skiplist show, to confirm they are already using skiplist format (so conversion has been made automatically). However /etc/sasldb2 is still in berkeley-hash format The question is how to specify auxprop format to use skiplist rather than berekeley ? I found that cvt_cyrusdb can be use to convert from one db format to another.

> what makes drop bdb support. What would be the replacement for it? skiplists. There was a long discussion about this on the cyrus mailing list several years ago (e.g. ~ 2010-09-28). BDB files are somewhat unstable and were causing all kinds of problems (e.g. filling up mail log files with junk like this: IOERROR: opening /var/lib/cyrus/user_deny.db: No such file or directory At that time it was decided the default would change to skiplist. I guess they finally decided to drop support for bdb. OTOH, I thought the old bdb files would be converted automatically to skiplists? BTW, you can't base anything on the Cyrus documentation. This is horribly out of date and generally quite inaccurate. The only place to find correct information is on the cyrus mailing list: info-cyrus@lists.andrew.cmu.edu Yes, I agree: cyrus would be a lot more popular if it had good documentation.

I checked the diff in libsasl, they are very few but I can't see what makes drop bdb support. What would be the replacement for it ? Cyrus-imap doc still recommends bdb http://cyrusimap.org/docs/cyrus-sasl/2.1.25/install.php (unless this is a new 2.1.26 undocumented feature)...

Hi, U'm sorry but I don't know why the Arch libsasl package has switched away from bdb. I have done a very quick search and I have found this "The Cyrus IMAP configure process attempts to automatically detect and use the latest Berkeley DB technology available on the system. This may, however, not be the same version on your production systems. Since database conversions between versions of the Berkeley DB technology are particularly difficult and therefor NOT considered fully supported, we recommend you do NOT use Berkeley DB." http://www.cyrusimap.org/~vanmeeuwen/cyrus-imapd-2.4-docs/Deployment_Guide/html/sect-Deployment_Guide-Supported_Platforms_and_System_Requirements.html Right now, I haven't got the time to update the cyrus-imap package but I might try and find the time in the next week or two. Alternatively drop an updated PKGBUILD yourself, but I fear this has serious implications for those already running cyrus-imap with a bdb (like me). I am not sure what's involved in upgrading. One for the "to do" list...

Hello, Since libsasl upgrade (2.1.26-6 -> 2.1.26-7) , sasldb auxiliary property plugin (the default one using Brekeley DB) no longer works. I opened a ticket for that, https://bugs.archlinux.org/task/38920 but it was closed abruptly. I don't understand the explanation given. I had to revert to libsasl 2.1.26-2. Any idea ? Thanks