> Therefore, qmail-smtpd modified with the patch will require two
> "checkpassword" type arguments, one to handle simple passwords, the other
to
> handle CRAM-MD5.
>
> Dabrowski also wrote his own replacement for checkpassword, cmd5checkpw,
> specifically to handle the CRAM-MD5 scheme. However, the latest version
of
> cmd5checkpw also handles simple passwords, so it can be used for both
> purposes. My qmail-smtpd start-up script looks like this:
>
> ... /var/qmail/bin/qmail-smtpd \
> /bin/cmd5checkpw /bin/true /bin/cmd5checkpw /bin/true ...
>
> Note that if you do use cmd5checkpw, you will have to create a new
password
> file that stores passwords unencrypted; the default is /etc/poppasswd.
The
> source package for cmd5checkpw provides an example to help you set up this
> new password file. Details and downloads at:
Kris,
I wanted to avoid using the cmd5checkpw program as I didn't want to have two
sets of password files to update. Also I'm using Outlook Express so that
means plaintext passwords only (?) - so I only put one argument on the
qmail-smtpd line. I was going to install the predecessor, that only has
plaintext auth - but that was a qmail-smtpd.c program only, and I wanted to
keep my patch for Qmail-Scanner - or can I install the new qmail-smtpd.c
program and then install the qmail-scanner patch ?
Or is there another way to force the program to check the POP3 passwords?
Cheers
John
