Lucky Leavell writes:
OS: SuSE 9.2 Pro
MTA: Postfix 2.1.5 (with MySQL support)
Courier-IMAP v3.0.7
maildrop v1.8
I setup maildrop according to the POSTFIX MAILDROP_README for direct
delivery without the local delivery agent. The test user is a virtual user
whose mail is stored under /home/vmail/te...@domain.tld/. If I specify
delivery via postfix virtual, it is delivered just fine. (I want to use
maildrop to allow mail filtering for virtual users though no filtering is
in effect yet, i.e., there are no mailfilter files.)
The entry in /etc/postfix/master.cf is verbatim from the MAILROP_README
with the path to maildrop corrected.
However, when I try to send mail to the test user, the following error
shows up in my mail log:
Apr 15 20:46:00 mail1 postfix/pipe[7541]: 44C5B36F8D:
to=<te...@domain.tld>, relay=maildrop, delay=0, status=bounced
(user unknown. Command output: Invalid user specified. )
I am using MySQL to store information on virtual users which is working
with both postfix and courier-imap. I suspect my problem has to do with
maildrop's not using MySQL to retrieve or validate user info.
Is my analysis correct?
If so, how do I make maildrop work with information stored in MySQL?
The easiest way is to upgrade to the current version of Courier-IMAP and
maildrop, where the authentication code has been moved to a separate new
package, courier-authlib, that both Courier-IMAP and maildrop will use.
2 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Invalid User Error
