Hi im using courier-imapd and want to use it to auth my users through mysql. As i installed pgsql because on of my users wants it, and i also wanted to have the abbility to use pgsql in othe apps , i added it to the USE Flag. Now after recompiling courier-imapd, i found out that the /etc/init.d/autdaemond just starts the pgsql driver but not the mysql driver, because it comes first in an elseif test. Im wondering why there arent more then one authenticator at the time supported, and if not, perhaps this can be configured in /etc/conf.d/ or so Martin
Grrr. I upgraded Courier-IMAP, and now it doesn't auth at all -- and I'm using a standard PAM authentication, I think -- at least, *I* didn't ask for msql or pgsql authentication. Tell me why, again, I'm using Courier-IMAP? Because I'm a masochist? Because I don't have anything better to do than waste my time with it? Because the Gentoo QMail distribution has been castrated and the IMAP support removed, so that Courier-IMAP is my only option?
Ok. Got it. Should I submit a new bug report? The problem is that IF you have postgresql, the courier-imapd.ebuild ASSUMES that you want to enable pgsql authentication. Which is a terrible, and wrong, assumption.
I just looked over the courier-imap init scripts... You are right, it looks as though there is a pecking order in the setauth() function in the authdaemond rc script... I am thinking that the best solution to this would be to have a file which contains your chosen authentication mechanism... This file can be sourced by the authdaemond script. If there is no authentication set, spit out an error message. If it is set, then the script runs with your chosen authenticator. If this sounds like a good solution to you, let me know... if not and you have a better idea, please let me know as well. :)
I have updated the authenticator choosing method so that things are configured via /etc/courier-imap/authdaemond.conf. The file is commented so you can change authenticators easily. I removed the postgres back end comment as it is not a supported authenticator. The new ebuild should be available in portage within 24 hours. Please test and report back on this bug emerge rsync emerge courier-imap
Let me add another problem here. Following the directions in the desktop guide, I changed the authentication to use "authpam", which no longer seems to work. I don't think that's a good thing, but I don't know what's broken.
I am currently using courier-imap with authpam without a problem. I only changed one line in /etc/courier-imap/authdaemonrc authmodulelist="authpam" The rest was set up ready to go after the ebuild finished installing. Some init and config file formats have changed so if you have installed courier- imap previously then I would suggest... emerge unmerge courier-imap rm -rf /etc/courier-imap rm /etc/init.d/courier-* emerge clean emerge rsync emerge courier-imap Let me know how things work for you after this.
I've found that re-emerging courier-imap (1.5.1) causes the directory: /var/lib/courier-imap/authdaemon to be deleted so authdaemon won't start. It gets installed fine on the first emerge. I can't spot any problem in the ebuild but hopefully someone else will know why. George.
All authentication problems appear to be addressed in the latest unmasked ebuild. With the latest version of portage emerging and re-emerging the software does not squash /var/lig/courier-imap/authdaemon.
