Jens Hassler <[EMAIL PROTECTED]> wrote:
> I'm using "checkpasswordnt" for my authentication issues (so that all users
> can be authenticated with our NT PDC). I just changed this back to the
> normal checkpassword program and tried again with an appropriate account.
> Now it works. No connection reset, nothing. So checkpasswordnt seems to make
> problems.
I concur. However, I don't know anything about checkpasswordnt.
> But, as I understand, checkpassword is only used to authenticate the
> connection in the first place. After that it's not accessed again? There
> seems to be some kind of timeout after one minute, but where?
>
> This is the ps aux output while running a pop3 session:
>
> root 6176 0.0 0.2 1224 344 pts/0 S 11:43 0:00
> /var/qmail/bin/qmail-popup wetzel-office.com /bin/checkpasswordnt
> /var/qmail/bin/qmail-pop3d Maildir
> jhassler 6177 0.0 0.3 1236 396 pts/0 S 11:43 0:00
> /var/qmail/bin/qmail-pop3d Maildir
I don't understand this. I thought that in a normal setup, tcpserver forked
qmail-popup, which exec's checkpassword, which exec's qmail-pop3d. In the
case of a successful authentication, the checkpassword process replaces itself
with qmail-pop3d, so it can't be left hanging around like this.
Is checkpasswordnt fundamentally broken?
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
Any opinions expressed are just that -- my opinions.
-----------------------------------------------------------------------
