Auth errors after upgrading courier-imap 3.0.8->4.0.1

Message

Souperman · Post by **Souperman** » Sat Feb 05, 2005 10:43 am

I've just upgraded courier-imap from 3.0.8 to 4.0.1 and now pam authenticaction no longer works. I figured out that I had to move auth* files from /etc/courier-imap/ to /etc/courier-authlib/, but I still get this in my /var/log/mail.log:

Code: Select all

Feb  5 12:29:54 wizard authdaemond: modules="authmysql authpam", daemons=5
Feb  5 12:29:54 wizard authdaemond: Installing libauthmysql
Feb  5 12:29:55 wizard authdaemond: Installation complete: authmysql
Feb  5 12:29:55 wizard authdaemond: Installing libauthpam
Feb  5 12:29:55 wizard authdaemond: libauthpam.so: cannot open shared object file: No such file or directory

courier-imap doesn't seem to have a USE flag for pam support. How do I get this to work again? For what it's worth, virtual mailbox accounts are still able to auth because the MySQL auth module is working just fine.

Souperman · Post by **Souperman** » Sat Feb 05, 2005 10:47 am

OK, got it to work with authshadow. Is this "The Right Way"tm ?

j-m · Post by **j-m** » Sat Feb 05, 2005 10:56 am

Souperman wrote:OK, got it to work with authshadow. Is this "The Right Way"tm ?

Looks you have some error in your config files.

Feb 5 11:53:55 gw authdaemond: modules="authmysql authpam authshadow authcustom", daemons=5
Feb 5 11:53:55 gw authdaemond: Installing libauthmysql
Feb 5 11:53:55 gw authdaemond: Installation complete: authmysql
Feb 5 11:53:55 gw authdaemond: Installing libauthpam
Feb 5 11:53:55 gw authdaemond: Installation complete: authpam
Feb 5 11:53:55 gw authdaemond: Installing libauthshadow
Feb 5 11:53:55 gw authdaemond: Installation complete: authshadow
Feb 5 11:53:55 gw authdaemond: Installing libauthcustom
Feb 5 11:53:55 gw authdaemond: Installation complete: authcustom

ryceck · Post by **ryceck** » Sat Feb 05, 2005 11:26 am

I solved this problem by removing the entries about authldap and authmysql since I dont use them.
This at least solved my problem and made authdaemon startable again.
I also removed the /etc/init.d/authdaemond script since there now is a /etc/init.d/courier-authd

Souperman · Post by **Souperman** » Sat Feb 05, 2005 11:27 am

OK, here's my configs for courier-authlib, minus comments and excluding authmysqlrc, since mysql auth isn't a problem.

/etc/courier/authlib/authdaemonrc wrote:

Code: Select all

authmodulelist="authmysql authshadow"
authmodulelistorig="authcustom authcram authuserdb authmysql authpam"
daemons=5
version=""
authdaemonvar=/var/lib/courier-imap/authdaemon

/etc/courier/authlib/authdaemond.conf wrote:
Code: Select all
AUTHDAEMOND="authdaemond.mysql"

nobspangle · Post by **nobspangle** » Sat Feb 05, 2005 12:40 pm

After upgrading my courier-imap was suddenly trying to authenticate against mysql.
I changed /etc/courier/authlib/authdaemonrc to have the line

Code: Select all

authmodulelist="authshadow authpam"

now all is well again.

Souperman · Post by **Souperman** » Sat Feb 05, 2005 1:11 pm

Well for some reason libauthpam.so isn't built when I emerge courier.

j-m · Post by **j-m** » Sat Feb 05, 2005 1:47 pm

Souperman wrote:Well for some reason libauthpam.so isn't built when I emerge courier.

Code: Select all

USE="crypt" emerge courier-authlib

Souperman · Post by **Souperman** » Sun Feb 06, 2005 9:17 am

Added the pam use flag for courier-authlib. Works now.

thanks

letoff · Post by **letoff** » Sun Feb 06, 2005 2:30 pm

Thanks to this thread, I've been able to solve the same problem: after an emerge from courier-imap-3.0.8 to 4.0.1 all authentication failed. So I first removed authdaemond from the default level and add courier-authlib instead. But authentication still failed. Then I remove all but authpam and authshadow in authdaemonrc and everything works fine. So thanks to all of you guys.

Nonetheless does any of you know how-to avoid this kind of problem in the future? I mean what documentation do we have to read before emerging such important paquage as emerge -pvl isn't enough?

tia.

justanothergentoofanatic · Sun Feb 06, 2005 4:24 pm

Here:
http://www.courier-mta.org/imap/?INSTALL.html~upgrading

I agree that the ebuild should have done this automatically, but it's not the most widely used or best tested ebuild in all of gentoo.

-Mike

fvant · Post by **fvant** » Sun Feb 06, 2005 7:41 pm

just gone through the motions

of the upgrade..leaving me with a question:

are pam_mysql and cyrus-sasl still required or has courier-authlib taken over their functionality ?

justanothergentoofanatic · Sun Feb 06, 2005 7:51 pm

As far as I know, they were never necessary. Courier has had TLS and MySQL authentication built-in for quite a while.

You can use authmysql instead of pam_mysql and either imapd w/TLS or imapd-ssl w/SSL instead of cyrus-sasl.

-Mike

Souperman · Post by **Souperman** » Sun Feb 06, 2005 7:55 pm

Although you may still need them if you're using postfix like me.

fvant · Post by **fvant** » Sun Feb 06, 2005 7:59 pm

i am in fact using postfix, never mind, i still need them

jeffrice · Post by **jeffrice** » Tue Feb 08, 2005 2:33 am

One additional point -- it may be necessary to copy authmysqlrc to /etc/courier/authlib. That got it working for me.

thoughtform · Post by **thoughtform** » Thu Feb 10, 2005 4:33 pm

i'm stuck.
since the upgrade i've been in various config files but squirrelmail is kicking me out with
Error connecting to IMAP server: localhost.
111 : Connection refused
i'm not sure where to start to fix this.

thanks,

Scorpaen

i'mtrying to use authpam or authshadow
/etc/courier/autlib/authdaemonrc
snippet -
authmodulelist="authpam authshadow"

thoughtform · Post by **thoughtform** » Thu Feb 10, 2005 5:00 pm

i rebooted and it's working.
can anyone explain why? i restarted the courier authdaemon.
???

Auth errors after upgrading courier-imap 3.0.8->4.0.1

Auth errors after upgrading courier-imap 3.0.8->4.0.1

i'm still having trouble...

solved