http://switch.richard5.net/2006/01/22/upgrading-the-courier-auth-module-to-058/ How to build your Mac into a internet server using open source software Tue, 17 Jun 2008 18:25:42 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://switch.richard5.net/2006/01/22/upgrading-the-courier-auth-module-to-058/comment-page-1/#comment-16126 Richard5 Fri, 02 Feb 2007 14:36:55 +0000 http://switch.richard5.net/?p=66#comment-16126 I don't know, you can always pickup the latest version and install it over your current one. I don’t know, you can always pickup the latest version and install it over your current one.

]]> http://switch.richard5.net/2006/01/22/upgrading-the-courier-auth-module-to-058/comment-page-1/#comment-16013 Eric Le Baron Thu, 01 Feb 2007 17:13:23 +0000 http://switch.richard5.net/?p=66#comment-16013 How do you know which version of the Courier-Auth module you have? How do you know which version of the Courier-Auth module you have?

]]> http://switch.richard5.net/2006/01/22/upgrading-the-courier-auth-module-to-058/comment-page-1/#comment-871 Kozman Bálint Mon, 29 May 2006 22:16:34 +0000 http://switch.richard5.net/?p=66#comment-871 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. <em> <strong>Richard5:</strong> 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.</em> 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.

]]>