13 messages in net.sourceforge.lists.courier-usersRe: [courier-users] multi-recipient b...
FromSent OnAttachments
Ricardo KleemannMay 30, 2005 3:37 pm 
Sam VarshavchikMay 30, 2005 3:58 pm 
Ricardo KleemannMay 30, 2005 4:20 pm 
Ricardo KleemannMay 30, 2005 4:21 pm 
Sam VarshavchikMay 30, 2005 5:12 pm 
Ricardo KleemannMay 30, 2005 6:06 pm 
Sam VarshavchikMay 30, 2005 6:22 pm 
Gordon MessmerMay 30, 2005 10:10 pm 
Sam VarshavchikMay 31, 2005 6:17 am 
Ricardo KleemannMay 31, 2005 6:33 am 
Sam VarshavchikMay 31, 2005 6:37 am 
Ricardo KleemannMay 31, 2005 7:49 am 
Sam VarshavchikMay 31, 2005 8:32 am 
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] multi-recipient bounce (re-post)Actions...
From:Ricardo Kleemann (rica@americasnet.com)
Date:May 31, 2005 6:33:57 am
List:net.sourceforge.lists.courier-users

Hi Sam,

On May 30, 2005, at 6:21 PM, Sam Varshavchik wrote:

Obviously that stupid mail server thinks the message is a bounce message for some other reason. Now, there is one situation where Courier may use a null envelope sender in this situation -- if the message was generated with DSN NOTIFY=NONE, and the receiving mail server does not support ESMTP DSNs.

What about the situation where the destination address was actually the member of an alias on the system running Courier? If I remember correctly, Courier also sends messages to alias recipients with a null envelope sender.

This is a message sent to a remote server. The logs show this is not the case.

I'm a little confused here. What Gordon mentioned above is correct... this is a majordomo list, and the recipients of the list are in an include file for an alias. So it is true that the destination addresses are all members of an alias on my server. Would, in this case, the envelope sender be null?

Ricardo