allenej at squeakerbill
Jul 6, 2002, 12:08 PM
Post #11 of 11
This is probably the way to go. I have a checkpassword program for dbmail that
works with the SMTP-AUTH patch, but it does not maintain a presistant
database connection. Any ideas on how to do this (I have tons, they're all
just about as expensive as opening a new database connection) would be
Go to http://www.squeakerbill.com/dbmail/ to get it.
Side Note: Is there a repository for 3rd party dbmail software? If not, I
would be happy to maintain one.
On Saturday 06 July 2002 5:56 am, Ryan Butler wrote:
> On Fri, 2002-07-05 at 20:59, Edward Allen wrote:
> > The problem is avoided completly if postfix (or qmail) asks for a
> > password INDEPENDENT OF DBMAIL. This means that it would either need to
> > use a seperate username table (It would be easy, I think, to write a perl
> > script to convert the dbmail auth tables to a format postfix can read).
> > In qmail, the smtp-auth patch uses a check-password program (which is
> > even easier to write a perl script to act as). I will post a link to a
> > check-password program for qmail with smtp/auth, as well as all of my
> > scripts in the next couple of days (and mirrors to relevent pages).
> There's already a perl daemon for use with SASL called mypwcheckd that
> will allow Postfix to use the dbmail user tables for SMTP AUTH. I've
> got a system with postfix, SMTP AUTH, TLS, and dbmail working nicely.
> Of course you need to use either AUTH PLAIN or AUTH LOGIN which are
> unencyrpted as SASL only supports secure AUTH through CRAM-MD5 or
> DIGEST-MD5 algorithms. But if you're using TLS as well, this isn't
> really a big deal since the whole session is encrypted
> Ryan Butler
> ADI Internet Solutions
> rbutler [at] adiis
> Dbmail mailing list
> Dbmail [at] dbmail