7 messages in net.sourceforge.lists.courier-users[courier-users] Re: another question ...
FromSent OnAttachments
Gordon MessmerJul 25, 2003 3:32 pm 
Sam VarshavchikJul 25, 2003 7:18 pm 
Gordon MessmerJul 30, 2003 6:15 pm 
Bowie BaileyJul 31, 2003 7:23 am 
Sam VarshavchikJul 31, 2003 8:11 am 
Gordon MessmerAug 3, 2003 6:42 pm 
Sam VarshavchikAug 3, 2003 8:10 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:[courier-users] Re: another question raised by usersActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Jul 25, 2003 7:18:39 pm
List:net.sourceforge.lists.courier-users

Gordon Messmer writes:

Courier seems to expand all external addresses in aliases so that the DSN value is set to "NEVER" (NN in the control file). It'll then deliver the message to the external address with either an empty return path, or NOTIFY=NEVER, depending on whether or not the remote server supports the DSN extension.

Is this desirable?

Yes. As far as the sender is concerned, the message has been delivered to the recipient. The sender does not care that one of the recipient addresses is an alias, which then forwards the E-mil to a nonexistent address that bounces.

What if the destination is an alias on a remote server? Will that not prevent users from seeing delivery failures that occur after the first hop?

Precisely. I can't tell you how many times some idiot sets up a forward to a full mailbox, and I get the totally useless bounce, as far as I'm concerned.