24 messages in net.sourceforge.lists.courier-usersRe: [courier-users] authdaemon problems
FromSent OnAttachments
Samuel PennJun 26, 2004 6:38 am 
Samuel PennJun 26, 2004 9:21 am 
Arturo "Buanzo" BusleimanJun 26, 2004 9:31 am 
Samuel PennJun 26, 2004 11:55 am 
Sam VarshavchikJun 26, 2004 12:16 pm 
Samuel PennJun 26, 2004 2:01 pm 
Sam VarshavchikJun 26, 2004 2:23 pm 
Samuel PennJun 26, 2004 3:10 pm 
Sam VarshavchikJun 26, 2004 4:54 pm 
Samuel PennJun 27, 2004 1:11 am 
Samuel PennJun 27, 2004 2:05 am 
Eric N. ValorJul 15, 2004 1:28 am 
Sam VarshavchikJul 15, 2004 4:05 am 
Eric N. ValorJul 15, 2004 9:11 am 
Eric N. ValorJul 15, 2004 12:29 pm 
Eric N. ValorJul 15, 2004 1:56 pm 
Sam VarshavchikJul 15, 2004 3:46 pm 
Eric N. ValorJul 15, 2004 5:30 pm 
Sam VarshavchikJul 15, 2004 6:19 pm 
Phillip HutchingsJul 15, 2004 6:21 pm 
James N. HartJul 15, 2004 6:49 pm 
Eric N. ValorJul 15, 2004 7:06 pm 
Sam VarshavchikJul 15, 2004 7:47 pm 
Eric N. ValorJul 17, 2004 1:42 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] authdaemon problemsActions...
From:Samuel Penn (sa@bifrost.demon.co.uk)
Date:Jun 26, 2004 11:55:44 am
List:net.sourceforge.lists.courier-users

On Saturday 26 June 2004 17:18, Samuel Penn wrote:

On Saturday 26 June 2004 14:35, Samuel Penn wrote:

First, if I try to start things from the init script, things seem to hang when starting courierfilterd:

Misreading the Gentoo init script, it's actually authdaemon that's hanging. There's a /usr/lib/courier/authlib/authdaemond.plain, which is hanging from /etc/init.d/courier.

There's also a /usr/lib/courier-imap/authlib/authdaemond.plain which is successfully started (with 5 children) from /etc/init.d/authdaemond.

Further investigation:

The one that works is linked against /usr/lib/libdb-3.2.so, that one that doesn't is linked against /usr/lib/libgdbm.so.2

Changing which one runs only affects whether it hangs at startup or not. They don't have any effect on the 'service temporarily unavailable' error I get from esmtpd.

Further playing with authtest (since I think it's got to be authdaemon related) shows that:

authtest -s esmtp -m authdaemon sam <password>

Gives a successful result, whilst

authtest -s esmtp -m authpam sam <password>

fails. There is a /etc/pam.d/esmtp file which looks vaguely correct (I don't know enough about PAM to know for sure):

auth required pam_nologin.so auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth session required pam_stack.so service=system-auth

Any call to authtest with the authpam module will fail, regardless of the service selected. In authdaemonrc, 'authpam' is selected, so I'm guessing something is wrong with PAM, though I don't know what. The installation notes say that special work is only needed for webmail. Do users need setting up in pam? Does a service need to be running?

I assume pam is being used to lookup a user's home directory in order to find where to put mail. I'm not (knowingly) using any authentication for esmtp, since everything is local to the machine (fetchmail->esmtp).

As long as a mail is sent to one of the accepted domains, will it be forwarded to an account of that user's name, regardless? So mails to sam@glendale... and sam@bifrost... both go into the home directory for user 'sam'?

Arturo, I also had an empty backuprelay file, which I've now deleted. A different error has now gone away, so that's solved things for once all the above has been fixed. Thanks.