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
Interesting. I checked a couple of my boxes and it was in the sasl
group.
--
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
Server Team, which is subscribed to
OK. Confirmed. All the boxes I have were upgraded from Hardy. If I
remove /etc/sasldb2 and recreate it in Intrepid it's root:root. If I do
it on a Hardy box it's root:sasl.
** Summary changed:
- Ownership of /etc/sasl2db precludes direct access by Cyrus IMAP
+ Ownership of /etc/sasl2db is
Hi,
The cyrus user *is* in the sasl group. However the permissions on
/etc/sasldb2 are root.root.
I believe this should either be cryus.sasl or as a minimum root.sasl
TTFN
Barry
Scott Kitterman wrote:
Interesting. I checked a couple of my boxes and it was in the sasl
group.
--
Adding cyrus to the sasl group should also solve it. I don't think this
is an actual bug in cyrus-sasl2.
--
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
Server Team,
