Thx for answer.
Ermmm iam not using /etc/passwd for my users...i use /etc/pop3pw
The file look like [name]:[password]:[NULL]:[Homedir]: for example
charles:secret:0:/home/pop3/charles: .
Charles
> -----Original Message-----
> From: Kris Kelley [mailto:[EMAIL PROTECTED]]
> Sent: Donnerstag, 14. Dezember 2000 21:08
> To: QMail Mailing List
> Subject: Re: RE : Smtp AUTH
>
>
>
> ----- Original Message -----
> From: "Charles Trtanj" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, December 14, 2000 1:04 PM
> Subject: RE : RE : Smtp AUTH
>
>
> > Well i started the smtpd server with this command "tcpserver -c20 -x
> > /var/qmail/control/smtp.cdb -g18 -u81 -R -v 0 smtp
> > /var/qmail/bin/qmail-smtpd /bin/checkpasswd /bin/true /bin/cmd5checkpw
> > /bin/true".
>
> Virtually the same as mine, with one major exception. The latest
> version of
> cmd5checkpw handles both clear-text passwords and the CRAM-MD5 scheme, so
> I'm not using checkpasswd at all. While that's something to
> check, I doubt
> it's the cause of the problem you are having.
>
> > the server started and accepted connection via telnet. But at
> > the moment a windows-user tried with outlook to login on the
> smtpd-server
> > the server says "bad password or username". I looked at the
> messagelog and
> > find " checkpasswd : domain.de:ipnumber:port user "" no $HOME, access
> > denied". But on my first configuration (smtp after pop) all was ok. The
> user
> > had first to login with pop3 and after that he can send emails.
>
> Yes, SMTP-after-POP schemes do not require the client to have any special
> knowledge about what's going on. ESMTP AUTH of course requires the client
> send the proper authentication information. I just sent a message through
> my AUTH-enabled server using Outlook, and it went without a hitch. Same
> with Outlook Express, which I use daily.
>
> Since the error message mentioned something about no $HOME, you
> may want to
> look at whatever checkpasswd is using to look up user information
> (/etc/passwd, presumably) and make sure this person actually has a home
> directory set. Then, if checkpasswd is as paranoid as qmail,
> make sure that
> the person actually owns his home directory, and that the directory is not
> world-writable.
>
> If none of this fixes the problem, you might want to post a
> question to the
> password mailing list. See http://cr.yp.to/lists.html#password
> for details.
>
> Good luck!
>
> ---Kris Kelley
>
>
