Martin Byrne wrote, on 08. feb 2007 11:51:
[...]
maildrop itself goes to authdaemond through libcourierauth for its
verification and quota routines, but authdaemond has to be configured
first. If that works, Courier IMAP ought to work too (after
configuration ;)
--Tonni
Authlib *is* working (using mysql) and has been working fine for the
past 2 years. If I run authtest valid.user@virtual.domain - it returns
successfully.
Ok.
My problem isnt with authlib per say but with maildrop using authlib.
When I build maildrop and run maildrop -v , Im expecting a message
stating either authlib or mysql support available. I get neither.
Where in the doco does it say that 'maildrop -v' will return that
"either authlib or mysql support available"?
1283 [root:tru.leerlingen] /# maildrop -v
maildrop 2.0.3 Copyright 1998-2005 Double Precision, Inc.
GDBM extensions enabled.
Courier Authentication Library extension enabled.
Maildir quota extension enabled.
This program is distributed under the terms of the GNU General Public
License. See COPYING for additional information.
What does yours say? (Bit like getting blood out of a stone, this ...)
Do you have an /etc/maildroprc? If so, what's in it? (grep '^[^#]'
/etc/maildroprc)
Also
if I run maildrop -d valid.user@virtual.domain - the message "Invalid
user specified" is returned.
Well, that goes without saying ... we need Brian Candler here, but he's
not a maildrop aficionado ...
--Tonni
18 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Cant get maildrop to ...
