2 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Configuring postfix /...
FromSent OnAttachments
ruslanMay 1, 2002 9:32 am 
Richard JohnsonMay 3, 2002 8:04 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] Configuring postfix / maildrop / userdb / courier-imapActions...
From:Richard Johnson (rdu@river.com)
Date:May 3, 2002 8:04:43 am
List:net.sourceforge.lists.courier-maildrop

At 17:30 +0100 on 01/05/2002, ruslan wrote:

thi command '# maildrop -v' shows:- GDBM extensions enabled Maildir quota enabled Virtual user database enabled

Thanks for the really big hint there. My 'invalid' user problem was caused by a db mismatch.

maildrop's configure will fall back to using berkeley db if it can't find gdbm. I hadn't noticed it had done so on my openbsd box.

However, the makeuserdb from courier-imap had found gdbm. maildrop couldn't read the results in userdb.dat.

Turns out the maildrop port's make environment is missing 'CONFIGURE_ENV = LDFLAGS="-L${LOCALBASE}/lib" CPPFLAGS="${CFLAGS} -I${LOCALBASE}/include"'.

Fixing that glitch (not really a bug, since --with-userdb isn't enabled by default in the maildir port) gave me a maildrop that could read from gdbm userdb.dat.

Thanks again for clueing me in on checking the db configuration that actually got built. :-)

Richard