I am running qmail with vpopmail. I also use the smtp authentication for users connecting from outside to qmail-smtpd and I use vchkpw to check user passwords. However, vchkpw does not support CRAM authentication and qmail-smtpd advertizes the AUTHCRAM capability. What happens is that if a user decides to login using CRAM they are always denied access. I suggest the following little patch to the qmail ebuild. --- ./qmail-1.03-r13.ebuild 2003-11-07 05:23:27.000000000 +0900 +++ ./qmail-1.03-r13.ebuild 2003-11-19 22:35:46.000000000 +0900 @@ -6,3 +6,3 @@ -IUSE="ssl" +IUSE="ssl noauthcram" DESCRIPTION="A modern replacement for sendmail which uses maildirs and includes SSL/TLS, AUTH SMTP, and queue optimization" @@ -70,2 +70,3 @@ epatch ${DISTDIR}/qregex-starttls-2way-auth.patch + use noauthcram && sed -i -e 's/^#define AUTHCRAM//' ${S}/qmail-smtpd.c
Sorry, I submitted an old version. --- ./qmail-1.03-r13.ebuild 2003-11-07 05:23:27.000000000 +0900 +++ ./qmail-1.03-r13.ebuild 2003-11-19 22:38:35.000000000 +0900 @@ -6,3 +6,3 @@ -IUSE="ssl" +IUSE="ssl noauthcram" DESCRIPTION="A modern replacement for sendmail which uses maildirs and includes SSL/TLS, AUTH SMTP, and queue optimization" @@ -42,2 +42,3 @@ ssl? ( >=dev-libs/openssl-0.9.6g ) + noauthcram? ( >=sys-apps/sed-4 ) >=net-mail/queue-fix-1.4-r1" @@ -70,2 +71,3 @@ epatch ${DISTDIR}/qregex-starttls-2way-auth.patch + use noauthcram && sed -i -e 's/^#define AUTHCRAM//' ${S}/qmail-smtpd.c
coming in -r14
if you are feeling experimental, -r14 is now out. It's hardmasked until I personally test it some more, but it should work.
