Sam Varshavchik wrote:
Dan Horne writes:
OK, I am trying to get maildrop v2.01 to work with virtual users using
MySQL. I compiled maildrop using "WITH_AUTHLIB=yes". I have set
I don't know where you got that from. There's no such thing as
"WITH_AUTHLIB=yes" mentioned in maildrop's INSTALL documentation, and
I have no idea where you got it from.
To get mysql support built, you must install, and test, the
courier-authlib package, first. Right at the beginning of maildrop's
INSTALL you will read this:
• Courier Authentication Library - optional, for LDAP, MySQL, or
PostgreSQL support.
If the configure script detects that the Courier Authentication
Library is installed, support for courier-authlib gets automatically
compiled. Use the --disable-authlib option to manually disable
courier-authlib support.
When courier-authlib support is enabled, the -d option to maildrop
will look up the account using the Courier Authentication Library,
making it possible to store mail account configuration in an LDAP,
MySQL, or a PostgreSQL database. See the courier-authlib documentation
for more information.
I have done a ktrace on the "maildrop -d us...@example.com" command and
didn't find any place where it was looking for a maildropmysql.* file.
That's because things don't work this way in 2.0, any more.
See INSTALL.
Sam, that is the FreeBSD/NetBSD port flag that tells it to compile and
install the security/courier-authlib port before compiling and
installing mail/mailldrop port.
If I'm right and the OP is using the ports system they need to remove
both ports and cd into the ports directory for courier-authlib first and
run make config to reconfigure the port to include mysql support as
(unless this changed recently) it only includes userdb support if you
tell it install as part of the maildrop install rather than as its own step.
Once the courier-authlib port is installed, the maildrop port should
then be reinstalled with the WITH_AUTHLIB="yes" option set.