Completely missed it, but I got a comment from Geva who mentioned an error during compilation. When I checked the error I found out that there has been an upgrade, the latest version is 0.58 instead of the 0.57 I used when I started this setup.
The related documentation has been updated and if you want to upgrade you can just download the new source-code and run the build commands as documented. Don’t forget the command:
chmod o+x /usr/local/var/spool/authdaemon
After you installed the compiled binaries. Otherwise you’ll get the error: SASL authentication failure: cannot connect to Courier authdaemond: Permission denied.
I’ve upgraded my server as soon as I found out. I found no real problems after the upgrade. the only thing I did wrong is that I forgot the chmod command myself and got the error as documented above.
I’ve subscribed myself to the Courier mailing list and others to prevent missing important updates like this and other pieces of software we use.
- No related posts
May 30th, 2006 at 12:16 am
On many installations postfix chroots to a directory created by the initscript by default. This is the case for example on debian and derivatives. If so, the authdaemon socket will not be seen by postfix, and you’ll have to either bind mount it there, or make a hard link to the socket file, to get the whole thing working. Don’t forget to add the link/bind mount command to your postfix initscript, as the chroot environment is always (re-)created when postfix starts off.
Richard5: Just to clarify, there is no problem with a postfix on your Mac OS X System. It doesn’t run as root, it’s just the case on most other systems you need to worry about this. But it is nice to see that people using another OS still can use these articles.
February 1st, 2007 at 7:13 pm
How do you know which version of the Courier-Auth module you have?
February 2nd, 2007 at 4:36 pm
I don’t know, you can always pickup the latest version and install it over your current one.