39 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Re: Maildrop EX_TEMPFAIL
FromSent OnAttachments
ha...@newmail.tvnet.huJul 5, 2002 11:37 pm 
Derrick 'dman' HudsonJul 6, 2002 9:05 am 
ha...@newmail.tvnet.huJul 8, 2002 12:56 am 
ha...@newmail.tvnet.huJul 8, 2002 6:40 am 
Derrick 'dman' HudsonJul 8, 2002 7:07 am 
Ben RosengartJul 8, 2002 7:09 am 
Matthias AndreeJul 8, 2002 8:24 am 
Matthias AndreeJul 8, 2002 8:25 am 
Ben RosengartJul 8, 2002 8:35 am 
Matthias AndreeJul 8, 2002 8:51 am 
Sam VarshavchikJul 8, 2002 3:03 pm 
Ben RosengartJul 8, 2002 3:32 pm 
Sam VarshavchikJul 8, 2002 4:15 pm 
Matthias AndreeJul 8, 2002 5:10 pm 
Sam VarshavchikJul 8, 2002 6:09 pm 
Ben RosengartJul 8, 2002 6:20 pm 
Sam VarshavchikJul 8, 2002 6:28 pm 
Ben RosengartJul 8, 2002 6:44 pm 
Sam VarshavchikJul 8, 2002 6:51 pm 
ha...@newmail.tvnet.huJul 9, 2002 3:56 am 
Matthias AndreeJul 10, 2002 2:47 am 
Matthias AndreeJul 10, 2002 2:49 am 
Matthias AndreeJul 10, 2002 3:05 am 
Derrick 'dman' HudsonJul 10, 2002 7:40 am 
Matthias AndreeJul 11, 2002 2:51 am 
Derrick 'dman' HudsonJul 13, 2002 9:00 am 
Matthias AndreeJul 14, 2002 7:47 am 
Derrick 'dman' HudsonJul 15, 2002 8:19 pm 
Sam VarshavchikJul 15, 2002 9:19 pm 
Ben RosengartJul 16, 2002 6:52 am 
Sam VarshavchikJul 16, 2002 7:22 am 
Ben RosengartJul 16, 2002 8:09 am 
Ben RosengartJul 16, 2002 11:24 am 
Sam VarshavchikJul 17, 2002 9:59 am 
Ben RosengartJul 17, 2002 12:29 pm 
Matthias AndreeJul 17, 2002 3:27 pm 
Matthias AndreeJul 17, 2002 3:33 pm 
Matthias AndreeJul 17, 2002 3:34 pm 
Matthias AndreeJul 18, 2002 12:21 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] Re: Maildrop EX_TEMPFAILActions...
From:Matthias Andree (ma@dt.e-technik.uni-dortmund.de)
Date:Jul 8, 2002 5:10:48 pm
List:net.sourceforge.lists.courier-maildrop

Sam Varshavchik <mrs@courier-mta.com> writes:

Ben Rosengart writes:

On Mon, Jul 08, 2002 at 06:03:21PM -0400, Sam Varshavchik wrote:

I already gave my answer: it's the mail server's job to refuse mail for nonexistent recipients. The fact that some MTAs can't always do that only means that they should do that.

So qmail is out of the play.

So every mail server should learn to speak to every backend to which maildrop can speak? That seems awfully redundant.

It's more like the other way around: maildrop should know how to speak to whatever account database the mail server uses.

Oh, it can do that, but it fails to communicate its trouble back, because it exits with EX_TEMPFAIL even for PERMANENT error conditions, like: no such user (EX_NOUSER).

The MTA relies on its MDA to communicate trouble back, waiting for the queue entry to expire just does not cut it.

Some MTAs allow you to "bless" maildrop to the general delivery backend, and don't bother to check. This is usually the more efficient approach compared to tricking the regular delivery backend into using maildrop.

The interface is there, it's sysexits.h, and maildrop defeats it for no good reason. Some MTAs (Postfix) don't bother to reject mail for non-existent users at the /usr/sbin/sendmail interface, and in this case, mail will ly around for a week or so, when it should instead bounce right away, which it would if maildrop bothered to exit(EX_NOUSER).

TECHNICAL reasons to refuse my patch like "it can return EX_NOUSER even for temporary failures" are fine, I will look into things and fix them. POLICY reasons just impair the usefulness of maildrop. And that's sad.