5 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Temporary failures - ...
FromSent OnAttachments
mlJul 17, 2006 6:53 am 
Tony EarnshawJul 17, 2006 10:46 pm 
mlJul 18, 2006 2:34 am 
Tony EarnshawJul 18, 2006 5:31 am 
moussJul 30, 2006 4:02 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] Temporary failures - maildrop+LDAP+postfixActions...
From:mouss (use@free.fr)
Date:Jul 30, 2006 4:02:25 pm
List:net.sourceforge.lists.courier-maildrop

ml wrote:

Hi all,

I'm running:

- postfix 2.2.1, virtual_transport = maildrop - maildrop-2.0.2 - courier-imap-3.0.8-3 - cyrus-saslauthd - openldap2 as backend for all

I'm constantly getting those temporary failures: "(temporary failure. Command output: /usr/local/bin/maildrop: Temporary authentication failure.)"

This happens at that point when maildrop should deliver the email into the user's Maildir. But maildrop returns this temporary failure, the email remains in the postfix-queue. These emails will get delivered at the next requeue interval.

I started with maildrop-1.8.1, so my hope was that an upgrade to maildrop-2.0.2 would fix it, but it didn't. So I thought my ldap-directory was some kind of bootleneck, and added some indexes, still no cure. Some of You experienced the same issue with mySQL as backend ... and my ldap is working fine with all other applications.

Delivering mails via Commandline "maildrop -V 4 -d user@domain < testmail" does not produce those errors and works like a charm.

- Try running this command as the user who runs maildrop (the one in user= in master.cf), not as as root. - check authdaemon socket permissions (including permissions of all the parent directories) - check whether your maildrop is setuid

Has anyone figured out why these "temporary failures" might occur ? Is it rather a maildrop-issue or does it depend on the backend ? Any ideas, hints, solutions ?