Differences between version 30 and previous revision of CyrusNotes.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 30 | Last edited on Tuesday, October 5, 2004 8:22:29 pm | by VladislavNaumov | Revert |
| Older page: | version 29 | Last edited on Tuesday, September 21, 2004 1:31:36 pm | by CraigBox | Revert |
@@ -66,9 +66,10 @@
</pre>
In syslog:
<verbatim>
Oct 12 22:57:56 ''server'' perl: No worthy mechs found
-Oct 12 22:57:57 ''server'' cyrus/imapd[''number'']: cannot connect to saslauthd server: Permission denied
+Oct 12 22:57:57 ''server'' cyrus/imapd[''number'']:
+
cannot connect to saslauthd server: Permission denied
</verbatim>
''Another thing that tripped me up the second time around is the permissions on /var/run/saslauthd if you're using that as your auth mechanism - just make sure that cyrus can read it and all will be fine -- TomHibbert''
''The best way to do this IMO is to make a sasl group on your system, make cyrus a member of this group, and give /var/run/saslauthd/ group +x permissions (only needs +x in order to be able to get into the dir, the actual socket on /var/run/saslauthd/mux is world +rwx anyway). This way, if you have other apps that use sasl, you just need to make them members of the sasl group as well and they can also read the socket. This is, AFAIK, the way the debian packages normally handle this -- DanielLawson''
