Tony Earnshaw wrote:
søn, 03.07.2005 kl. 08.27 skrev Rob Brandt:
*cut*
Jul 2 15:47:29 linux postfix/pipe[18677]: 952C0638AE:
to=<rbra...@amd64.csd-bes.net>, relay=maildrop, delay=0, status=deferred
(temporary failure. Command output: ERR: authdaemon: s_connect() failed:
Permission denied /usr/bin/maildrop: Temporary authentication failure. )
I'm using "mailuser" as the maildrop user, which is the user that has access to
the maildirs.
Here are my main.cf and master.cf; there may be conflicting settings in them
because of the multiple configuring options, but I don't recognize them.
master.cf:
More important is, if you're using authlib and a recent version of
maildrop, how is authlib's authmysqlrc configured? maildrop uses this
now, not the old maildropmysqlrc or whatever it was (I use LDAP :)
Moreover: instead of worrying about logs too much, try saving a message
as a file from your MUA and doing 'maildrop -V[3-5] -d us...@domain.tld <
message.eml' and maildrop should spit out where it's going wrong.
I suspect the user 'maildrop' cannot read the authdaemon socket. It's
located in /usr/var/authdaemon/socket (using debian), but its location is
probably different with other distributions.
After using 'strace -o /tmp/maildropdebug maildrop -V5 -d us...@domain.tld
< message.eml', you can look at /tmp/maildropdebug to see the actual path.
In my case it looks like this:
connect(3, {sa_family=AF_FILE, path="/var/run/courier/authdaemon/socket"},
110) = 0
Make sure it's readable by the maildrop user, and a recursive chmod on
/var/run/courier should do the trick.
Good luck.
jasper
9 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Postfix/maildrop driv...
