Eric N. Valor writes:
I guess I am blocking on how to get Maildrop to verify that the
particular rcpt to: address is valid, and how to tell Maildrop where to
place the message under these circumstances.
I'm under the impression that Courier and Maildrop would use a single local (passwd) user to own the various Maildirs, differentiating based on the particular mail recipient address in question, as in:
/var/spool/courier/user1/ /var/spool/courier/user2/ /var/spool/courier/user3/
all owned by courier:courier, with user courier having home directory of
/var/spool/courier.
I'm not finding much documentation telling me how to make Maildrop look
in the LDAP database to verify the user (if that's what is needed).
Again, I apologize for not being clearer with my original request.
Use --enable-maildropldap to enable LDAP support in maildrop, then after installing maildrop set things up in /etc/maildropldap.config
However, you should reorganize things a bit. It's going to be a bit difficult to get maildrop working in such a configuration.
/var/spool/courier/user1, and /var/spool/courier/user2 are going to be the defined home directories of your virtual users. And, as you know, the default maildir is $HOME/Maildir, therefore you also need to create /var/spool/courier/user1/Maildir, and /var/spool/courier/user2/Maildir.
Since, as you know, /home/user1 would be the typical home directory of a system user, the user's $HOME/Maildir would therefore be /home/user1/Maildir. The analogy is quite clear: for your virtual user the home directory is /var/spool/courier/user1, and its $HOME/Maildir is /var/spool/courier/user1/Maildir. Similarly, for a system user, $HOME/.mailfilter, the maildrop recipe, is /home/user1/.mailfilter. For the virtual user, whose home directory is /var/spool/courier/user1, its $HOME/.mailfilter would therefore be /var/spool/courier/user1/.mailfilter.
pgpRHGkaWqwuv.pgp
Description: PGP signature
