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:Tony Earnshaw (teri@barlaeus.nl)
Date:Jul 17, 2006 10:46:06 pm
List:net.sourceforge.lists.courier-maildrop

ml skrev:

I'm running:

What OS and version is this? I used to get a lot of this on RHEL3 with OpenLDAP 2.2.17 installed from source. It's virtually all gone with RHAS4 and OpenLDAP 2.3.24 built from adapted Buchan Milne (Mandriva cooker) rpms.

- postfix 2.2.1, virtual_transport = maildrop

I have Postfix 2.3.0 with a local transport table (pipe) to maildrop. Nobody has his own login, the mail structure is owned by vmail.

- maildrop-2.0.2

Same here

- courier-imap-3.0.8-3

4.1.1 here, but that won't have anything to do with it

- cyrus-saslauthd

I don't use Cyrus saslauthd. This would be for Postfix or pam, since maildrop doesn't use any SASL code. Would you be authenticating with pam? maildrop can use pam, but I use authldaprc which lets me use quotas and a specified Maildir (neither possible with pam) and more (a compound attribute filter)

- openldap2 as backend for all

What OpenLDAP 2? If this is 2.0, you could be letting yourself in for much trouble.

--Tonni

--

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.

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 ?

Regards ML

_______________________________________________ Courier-maildrop mailing list Cour@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/courier-maildrop

-- tonni at barlaeus.nl Tony Earnshaw