Hi Chris,
On Mon, 16 Jun 2003 07:13:23 -0700 (PDT) Chris Pugh wrote:
>>> OK. Reference removed, even though its correct ..
>>> now it doesn't authenicate at all. Damn!
>> to quote Dave Sill "What do the logs say[TM]?" :-)
> Which one would you like, most of the mail ones are
> pretty normal, nothing untoward at all.
The one that shows e.g. "authentication failed", or anything similar.
In my expericence authentication seldom fails silently when using
vchkpw.
So I'd:
1.) Retire inetd and reactivate tcpserver.
2.) Set POP3 tcpserver to be _verbose_
3.) Check _all_ path
4.) Have a look in the file your syslog store messages of type 'mail.*'
in. If vchkpw fails to authenticate it logs this fact (unless you
have turned it off completely, which you havent, IFAICS)
5.) If nothing thelps I'd
printf "<UserName>\0<Password>\0QWERTZUIOP\0" | \
strace -s 4096 -f -o /tmp/vchkpw.log \
/home/vpopmail/bin/vchkpw /bin/true 3<&0; echo "Return: $?"
as 'root' or 'vpopmail' and if the number printed along with
"Return: " is not 0 I'd inspect '/tmp/vchkpw.log' where the check
failed.
Of course you'll have to replace '<UserName>' with a username that's
valid on your vpopmail installation, as well as '<Password>' needs
to be the approrpiate pass :-)
If, OTOH, you get 'Result: 0' you'll have to go figure, why vchkpw
failes when executed from inetd/tcpserver. Can be done by inserting
'strace' into vchkpw-call there too.
HTH
--
Ciao,
Pit
