From: Marcus Ilgner <[EMAIL PROTECTED]>
Date: Jul 5, 2006 11:17 AM
Subject: Re: [courier-users] getpw in authlib fails for courier-mta after recent update
To: Stefan Hornburg <[EMAIL PROTECTED]>
On 7/5/06,
Marcus Ilgner <[EMAIL PROTECTED]> wrote:
This is the complete log output from syslog:
Jul 5 11:02:36 anubis authdaemond: stopping authdaemond children
Jul 5 11:02:36 anubis authdaemond: modules="authpam authldap", daemons=5
Jul 5 11:02:36 anubis authdaemond: Installing libauthpam
Jul 5 11:02:36 anubis authdaemond: Installation complete: authpam
Jul 5 11:02:36 anubis authdaemond: Installing libauthldap
Jul 5 11:02:36 anubis authdaemond: Installation complete: authldap
Jul 5 11:03:07 anubis courieresmtpd: started,ip=[::ffff: 192.168.115.100]
Jul 5 11:03:07 anubis submit: getpw( *username of destination user* ) failed - returned by authlib.
Jul 5 11:03:07 anubis courieresmtpd: error,relay=::ffff: 192.168.115.100 ,from=<[EMAIL PROTECTED]>,to=<* [EMAIL PROTECTED]>: 450 Service temporarily unavailable.
Jul 5 11:03:07 anubis courieresmtpd: error,relay=::ffff: 192.168.115.100,msg="502 ESMTP command error",cmd: DATA
Somehow, getpw() fails while other applications are able to look up the homedir of a given user. All user data is stored in LDAP. But since PAM is used, I guess this should not matter. Still, Imapd is working fine.
Just wanted to add this comment to the 'LDAP' bit:
a search using `ldapsearch -x -h localhost homeDirectory` successfully returns all home directories using anonymous bind, so I'm pretty sure that LDAP can be ruled out as the source for this problem.
Greetings
On 7/5/06, Stefan Hornburg <[EMAIL PROTECTED]
> wrote:
Marcus Ilgner wrote:
> On 7/5/06, *Stefan Hornburg* <[EMAIL PROTECTED]
> <mailto: [EMAIL PROTECTED]>> wrote:
>
> Marcus Ilgner wrote:
> > Hello folks,
> >
> > after a recent update of courier-mta, the smtp daemon is unable to
> > retrieve my users home directory using getpw.
> > The authdaemon is set to use authpam and I can log in to imapd
> without
> > problems:
> >
> > courierd: getpw(*username*) failed - returned by authlib.
> >
> > Using `getent passwd` on the command line, I am able to list all
> users
> > together with their home directories.
> >
> > Debian package versions are
> > ii courier-authdaemon 0.58-3 Courier
> > authentication daemon
> > ii courier-authlib 0.58-3 Courier
> > authentication library
> > ii courier-base 0.53.2-3 Courier Mail
> Server
> > - Base system
> > ii courier-imap 4.1.1-3 Courier Mail
> Server
> > - IMAP server
> > ii courier-imap-ssl 4.1.1-3 Courier Mail
> Server
> > - IMAP over SSL
> > ii courier-maildrop 0.53.2-3 Courier Mail
> Server
> > - Mail delivery agent
> > ii courier-mta 0.53.2-3 Courier Mail
> Server
> > - ESMTP daemon
>
>
> Which Debian distribution do you use ?
>
> Bye
> Racke
>
>
>
> It's Debian testing, since I need some packages not available in the
> stable branch :/.
> Additionally, I have added packages from secure-testing.debian.net
> <http://secure-testing.debian.net> to my apt sources.list.
>
I just setup courier-mta on my new laptop with Debian testing and it
works "out of the box" with PAM. Can you sent the log entries from
the failed delivery ?
Thanks
Racke
This is the complete log output from syslog:
Jul 5 11:02:36 anubis authdaemond: stopping authdaemond children
Jul 5 11:02:36 anubis authdaemond: modules="authpam authldap", daemons=5
Jul 5 11:02:36 anubis authdaemond: Installing libauthpam
Jul 5 11:02:36 anubis authdaemond: Installation complete: authpam
Jul 5 11:02:36 anubis authdaemond: Installing libauthldap
Jul 5 11:02:36 anubis authdaemond: Installation complete: authldap
Jul 5 11:03:07 anubis courieresmtpd: started,ip=[::ffff: 192.168.115.100]
Jul 5 11:03:07 anubis submit: getpw( *username of destination user* ) failed - returned by authlib.
Jul 5 11:03:07 anubis courieresmtpd: error,relay=::ffff: 192.168.115.100 ,from=<[EMAIL PROTECTED]>,to=<* [EMAIL PROTECTED]>: 450 Service temporarily unavailable.
Jul 5 11:03:07 anubis courieresmtpd: error,relay=::ffff: 192.168.115.100,msg="502 ESMTP command error",cmd: DATA
a search using `ldapsearch -x -h localhost homeDirectory` successfully returns all home directories using anonymous bind, so I'm pretty sure that LDAP can be ruled out as the source for this problem.
Greetings
Marcus
P.S.: I have switched to authldap for the moment but it gives me some headache, too, since it makes the server output a "456 Address temporarily unavailable" every now and then. So I'd really like to get authpam back... :P
P.S.: I have switched to authldap for the moment but it gives me some headache, too, since it makes the server output a "456 Address temporarily unavailable" every now and then. So I'd really like to get authpam back... :P
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users