Alex Chekholko skrev, on 07-08-2007 04:41:
Alright, how about another approach that was suggested to me elsewhere
(but sadly, without details). There is a userdb in /etc/dovecot/userdb.
Is there a way to make maildrop understand that file somehow?
After all, that configuration even seems to be referred to in the
Postfix+maildrop howto: http://www.postfix.org/MAILDROP_README.html
I just don't understand what "match key for maildrop userdb lookup" means.
${user}@${nexthop} matches what's in the DB that Courier authlib is
using (userdb, pam, LDAP, SQL). Simple databases consist of key-value,
where key is what you look up on and value is what it returns (like a
phone catalog).
The parameters shown here in MAILDROP_README are those passed to
maildrop as environment values and which can be used in
maildroprc/.mailfilter.
Would that involve setting up courier-auth-userdb?
No, not necessarily. My sites use LDAP. The readme's simply referring to
the db used by authlib (see above). It was written years ago, when
maildrop had its own db mechanisms, before authlib came along.
Then configuring
that to parse the /etc/dovecot/userdb file?
Postfix can be built either with Cyrus or Dovecot for authentication.
Courier authlib (for that's what it's all about) has its own SASL code
and makes no use of external mechanisms, there's no way one can use the
above db.
Then configuring maildrop
to use courier-authlib-userdb? I can't find any useful tutorial through
the mighty Google. Anyone have a pointer? Or is this also not a good
way to accomplish this?
Not possible. By using (LDAP|pam|SQL) as base, one can use the same
database for maildrop/IMAP/Postfix. LDAP authentication, where the pam
and nss libraries come into play, can be used for 99% of all services
offered on a network, including for example Windows (via Samba), gdm
graphic logins, shell logins and much more. That's what my sites use, a
single login ID and password for all services on my sites.
--Tonni