12 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Any way for Couri...
FromSent OnAttachments
Jeff PotterDec 17, 2004 7:24 am 
Lindsay HaisleyDec 17, 2004 11:54 am 
Jeff PotterDec 17, 2004 2:44 pm 
Gordon MessmerDec 17, 2004 3:13 pm 
Sam VarshavchikDec 17, 2004 4:00 pm 
Martijn LievaartDec 18, 2004 2:44 am 
Sam VarshavchikDec 18, 2004 8:58 am 
Martijn LievaartDec 18, 2004 3:20 pm 
Jeff PotterDec 18, 2004 3:50 pm 
Julian MehnleDec 18, 2004 3:58 pm 
Sam VarshavchikDec 18, 2004 4:07 pm 
Lindsay HaisleyDec 18, 2004 5:34 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: [courier-users] Any way for Courier to run dot-courier before returning status code on SMTP layer?Actions...
From:Martijn Lievaart (m@rtij.nl)
Date:Dec 18, 2004 2:44:40 am
List:net.sourceforge.lists.courier-users

Sam Varshavchik wrote:

Jeff Potter writes:

Hi All,

I'm wondering if there's any way that Courier can do this:

1. Receive a message on SMTP 2. After getting ".<CR><LF>", but before responding "250 Ok"... 3. Attempt to deliver the mail: if there are delivery instructions in a .courier file, run them. 4. If one of the delivery instructions generates a hard error, on the SMPT layer respond with "5xx Unable to deliver message, local delivery instructions failed."

I know that Courier can check if dash-extension addresses are existent if the homedir is o+rx, but what I'm hoping is that this can be extended to actually *running* the users delivery instructions so that any DSNs that do get generated, get generated out the SMTP layer so that invalid from addresses don't cause double bounces to my local postmaster account.

Doable?

There's a similar facility that provides for executing a restricted maildrop recipe, which can examine the message's contents, and selectively accept or reject the message.

It's rather difficult/tricky to set up.

Begin by reading the localmailfilter man page. All of it. Paragraph by paragraph.

I looked at this previously and it does not seem to fit my bill completely.

Can I whitelist postmaster@ and abuse@ unconditionally? Or does "accept message onconditionally" only apply to the contentfilter but blocklists are still applied? I think the latter, as blocklists are applied earlier in the SMTP phase.

If I understand the manpage correct, these filters are not run for messages submitted on the MSA port?

Martijn