 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
5 messages in net.sourceforge.lists.courier-maildropRE: [maildropl] maildrop & MySQL (wit...| From | Sent On | Attachments |
|---|---|---|
| Kilian Huber | May 2, 2003 11:21 am | |
| Bernhard Schmidt | May 2, 2003 11:59 am | |
| p dont think | May 2, 2003 12:43 pm | |
| Kilian Huber | May 2, 2003 2:15 pm | |
| p dont think | May 2, 2003 2:41 pm |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | RE: [maildropl] maildrop & MySQL (with postfix) | Actions... |
|---|---|---|
| From: | p dont think (pdon...@angrynerds.com) | |
| Date: | May 2, 2003 2:41:10 pm | |
| List: | net.sourceforge.lists.courier-maildrop | |
call maildrop from postfix's master.cf with "pipe flags=Ru user=amavis argv=/usr/local/bin/maildrop -d ${user}", I get the error "temporary
I have "-d $recipient" (no braces)
but I think your problem is not this, but the "user=amavis"
there are several postings about getting the user correct in the mailing list archives. make sure that you created a user called amavis and you might also need to configure with --enable-trusted-users='amavis' depending on your --enable-restrict-trusted setting.
Yes, user amavis exists, amavisd runs with it. Should I use a different UID for maildrop? I recompiled maildrop with
I created a maildrop user and group, but I would think that you could get your amavis user to work. Per the documentation:
--enable-trusted-users='...' - sets the list of users allowed to use the -d option if --enable-restrict-trusted is set to 1. If --enable-restrict-trusted is set to 0, this option is not used. Put a list of user IDs allowed to use the -d option between the apostrophes, separated by single spaces. If your mail transport agent uses maildrop as the local delivery agent this list must include the userid that the mail transport agent runs as. If this option is not specified, maildrop attempts to put together a list including common mail system user ids.
Thus, maildrop is probably not guessing that "amavis" is a user that is allowed to use the -d flag. If you are "not using" the --enable-restrict-trusted flag, it is set to 1 as default, by the way.
--enable-trusted-users='amavis' but still no luck, though I'm not
using
To be complete, I made sure that both users and --enable-trusted-groups were set. You might want to check that, too.
--enable-restrict-trusted. Also tried $recipient without braces but that didn't help either. Is it correct that a maildropmysql.config is sufficient and that I do not need a system-wide maildroprc? I suspect
yes it is.
that maildrop doesn't even read maildropmysql.config, is there a way
to
it might not be if it's not getting that far, although I am not familiar with maildrop enough to know when that happens in relation to your error
check this? Also, what are you using as uid_field in your mail database? Is it the email-address or some other naming scheme?
uid? I am using the numerical uid, not a username. I have different uids for each user (such as 5001, 5002, etc), although many people have one uid for all virtual users... either way works fine. that could very well be your problem.
for database stuff, turn on mysql logging and watch the log file, which will be helpful
- paul