2 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Postfix + Mysql + mai...
FromSent OnAttachments
Jeff RiceNov 8, 2005 1:23 pm 
Sam VarshavchikNov 8, 2005 3:34 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] Postfix + Mysql + maildrop issuesActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Nov 8, 2005 3:34:26 pm
List:net.sourceforge.lists.courier-maildrop

Jeff Rice writes:

(temporary failure. Command output: /usr/bin/maildrop: You are not a trusted user. )

If I su to vmail, it seems like maildrop is OK -- so I assume that vmail was listed as a trusted user in the debian compile of maildrop.

That's not what a trusted user means. See maildrop's INSTALL.

Obviously there is an issue with the trusted users. Maildrop should run as "vmail", right?

Only if when you compiled maildrop you listed vmail as a trusted user. See maildrop's install.

And figure out where to deliver the mail via

courier-authmysql? I am confused by this aspect and have not been able to find a document that describes how to do this clearly enough that I can apply it to my setup.

You're trying to do too much at the same time, and only get yourself confused.

Begin by installing courier-authlib, and using its tools (authtest) to verify that authentication works, and looking up a mail accounts returns its correct home directory, userid, and groupid.

Only after you verified that courier-authlib is correctly configured, and it sees your accounts, then you can go ahead and install maildrop.

You must read maildrop's INSTALL, from the beginning. Don't assume that you can ignore it, and just hack things on your own. There are some important notes in maildrop's INSTALL that tell you what you need to do in order to correctly interface maildrop with your mail server.