John P. wrote:
> 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.
Regardless of your set-up, the patched version of qmail-smtpd will need two
checkpassword arguments. Since you won't be using CRAM-MD5 at all, you can
probably forego installing cmd5checkpw and simply give a dummy argument for
the second checkpassword requirement. So your script might look like this:
... /var/qmail/bin/qmail-smtpd \
/bin/checkpassword /bin/true dummy /bin/true ...
I would recommend that "dummy" be replaced with a program that always
returns failure, in case some smart-alec in your domain tries to use a
CRAM-MD5 enabled client.
> 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 ?
I am not using qmail-scanner, so I'm afraid I have no experience with it.
At any rate, using the original version of "Mrs. Brisby"'s qmail-smtpd is
not recommended, due to a bug that would allow anybody to relay if the
checkpassword program crashed. The latest version of Dabrowski's patch
fixes that bug.
---Kris Kelley
