> -----Original Message-----
> From: Roland Schneider [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 27, 2002 2:59 PM
> To: '[EMAIL PROTECTED]'
> Subject: Re: [courier-users] Cannot authenticate;
> userdb/authdaemond/FreeBSD
>
>
> --Yanek Korff wrote on 27.02.2002 10:02 -0500:
>
> > [EMAIL PROTECTED]
> >
> uid=61|gid=71|home=/web/mail|mail=/web/mail/test|shell=/bin/ba
> sh|systempw=[13charstring-letters&numbers]
>
> mail should be more something like 'mail=/web/mail/test/Maildir',
> and append a pipe to the line will kill trailing whitespaces.
That shouldn't matter, should it? I currently have it set as follows:
[EMAIL PROTECTED]
home=/web/mail/spinthread.com/test|mail=/web/mail/spinthread.com/test/Maildi
r|uid=61|gid=71|systempw=[***]|
I continue to see login failing.
> > I'm trying to authenticate using POP3, but: pop3d-ssl: LOGIN FAILED
> this message was not from pop3d, check your setup again.
Well it was from authdaemond.plain, really.
> > I am at a loss as to why authentication might be failing.
> I have tried user [EMAIL PROTECTED] and just user "test."
> There is no user 'test' in your userdb, waste of time :)
I'll stop testing that, then.
> Try the utility 'authtest' from the sources, and the utility
> authdaemontest.pl has to be somewhere in the archives.
Yeah, I've been checking that out. Note the -md5 still looks like a crypt
password. Is that normal? It still concerns me that authdaemon.plain NEVER
even looks at the userdbshadow.dat according to ktrace -- is THAT normal?
Take a look:
root:~> echo test123 | userdbpw | userdb
"[EMAIL PROTECTED]" set systempw
root:~> cat /usr/local/etc/userdb/spinthread.com
[EMAIL PROTECTED]
home=/web/mail/spinthread.com/test|uid=61|mail=/web/mail/spinthread.com/test
/Maildir|systempw=iD20LUZ7lgx2I|gid=71
root:~> makeuserdb
root:~> /usr/local/etc/rc.d/pop3d-ssl.sh stop
root:~> /usr/local/etc/rc.d/pop3d-ssl.sh start
root:~> cd /usr/ports/mail/courier-imap/work/courier-imap-1.3.12/authlib/
root:/usr/ports/.../authlib> ./authdaemontest 1 1 ./authtest
[EMAIL PROTECTED] test123
Authentication FAILED!
root:/usr/ports/mail/.../authlib> ./authtest [EMAIL PROTECTED] test123
Authentication FAILED!
root:/usr/ports/.../authlib> echo test123 | userdbpw -md5 | userdb
"[EMAIL PROTECTED]" set systempw
root:/usr/ports/.../authlib> cat /usr/local/etc/userdb/spinthread.com
[EMAIL PROTECTED]
home=/web/mail/spinthread.com/test|uid=61|mail=/web/mail/spinthread.com/test
/Maildir|gid=71|systempw=H6DT11bxVFXRA
root:/usr/ports/.../authlib> makeuserdb
root:/usr/ports/.../authlib> /usr/local/etc/rc.d/pop3d-ssl.sh stop
root:/usr/ports/.../authlib> /usr/local/etc/rc.d/pop3d-ssl.sh start
root:/usr/ports/.../authlib> ./authdaemontest 1 1 ./authtest
[EMAIL PROTECTED] test123
Authentication FAILED!
root:/usr/ports/.../authlib> ./authtest [EMAIL PROTECTED] test123
Authentication FAILED!
root:/usr/ports/.../authlib>
> You also could configure --without-authdaemon, much easier
> to debug with strace.
ktrace okay? Been using that -- easy enough to predict which authdaemon.
It always chooses the lowest pid.
-Yanek.
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
