5 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Rejecting mail
FromSent OnAttachments
David ChristianAug 8, 2002 10:51 am 
Sam VarshavchikAug 12, 2002 2:57 pm 
Tim KoenigAug 15, 2002 3:59 am 
Luc BrouardAug 15, 2002 12:37 pm 
Ben RosengartAug 15, 2002 2:20 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] Rejecting mailActions...
From:Ben Rosengart (br+c@panix.com)
Date:Aug 15, 2002 2:20:39 pm
List:net.sourceforge.lists.courier-maildrop

On Thu, Aug 15, 2002 at 09:33:50PM +0200, Luc Brouard wrote:

On Thu, Aug 15, 2002 at 12:58:20PM +0200, Tim Koenig wrote:

Both are using the exit-codes in <sysexits.h>. When Maildrop exits with EX_TEMPFAIL (this happens e.g. when the user given with -d is unknown), Postfix puts the offending mail into the "deferred" queue (RedHat Linux, other environments may show different behaviour).

This is the standard behavior of maildrop, to change that to have postfix reject the mail. You have to apply a patch from Matthias Andre (check the archive or google). Sam doesn't want to exit with EX_NOUSER when the user is not existing. (It saved me once not to lose some mail, but I think this is not the "right" behavior). He believes that it is the MTA job to reject unknown user from the start.

Here is a workaround for Postfix. If, in your userdb, each user's name is also their email address, you can run the userdb through awk:

awk '{print $1"\tOK"}' < userdb

and it will output a map suitable for use with Postfix. Call it "recipmap", say, and run "postmap recipmap", then, in main.cf, set up something like this:

smtpd_recipient_restrictions: [...], check_recipient_access hash:/path/to/recipmap, reject

Microsoft has argued that open source is bad for business, but you have to ask, "Whose business? Theirs, or yours?" --Tim O'Reilly