Jens E. Madsen Jr. writes:
Sam Varshavchik wrote:
Jens E. Madsen Jr. writes:
# maildrop -v9 -d te...@domain1.com
maildrop 2.0.2 Copyright 1998-2005 Double Precision, Inc.
GDBM extensions enabled.
Maildir quota extension enabled.
This program is distributed under the terms of the GNU General Public
License. See COPYING for additional information.
Actually, the command I really meant to type was:
# maildrop -V9 -d te...@domain1.com <<-- Capital V
Invalid user specified.
That's a different story.
maildrop works with system (unix account) users but not virtual users in
userdb.
I also checked the source archive I downloaded from the courier-mta.com
web site link and it appears that enable-userdb is set.
There's no such option in the current version of maildrop.
The current version of maildrop uses courier-authlib, which implements
userdb access.
So how can I test maildrop to be sure that it is using userdb? Does it
need any configuration in either /etc/maildroprc or another file?
For the current version of maildrop, you need to compile, install, and test,
courier-authlib first.
The tools in the courier-authlib will allow you to verify that the account
database is properly set up, i.e. "tes...@domain.com" is recognized as a
valid mailbox name.
Once you've set up courier-authlib, you will need to recompile maildrop.
6 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Simple maildrop using...
