Hi, Im not sure that will help as the permissions of the installed sasldb are root.root with no acl on it.
Perhaps the issue is two-fold, the cyrus-common-2.2 install (which I think creates the user) should include the sasl group permission for the cyrus user, and cyrus-sasl2 should correct the group access on the /etc/sasldb2 file to be root.sasl ? Is it expected that all access will go through saslauthd? I used to run this but changed to having the imap service access the sasldb directly which saves memory etc as there is no need for me to run the saslauthd service at all. Or does this come under one of those cross-package configuration issues that are basically resolved by hand? Cheers, Barry Scott Kitterman wrote: > Adding cyrus to the sasl group should also solve it. I don't think this > is an actual bug in cyrus-sasl2. > > -- Sincerely Yours Copyright Witness Net Support [EMAIL PROTECTED] www.copyrightwitness.com Registration centre for copyright works. This e-mail and any attachments are confidential and intended for the addressee only. The information in this mail does not amount to legal advice or opinion. Any views or legal references are those of the author and are based on personal opinion or understanding only. -- Ownership of /etc/sasl2db precludes direct access by Cyrus IMAP https://bugs.launchpad.net/bugs/288478 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
