Ricardo Kleemann writes:
That's maybe what the From: header says. Which is completely
irrelevant.
What you need to know is the envelope return address.
Well actually I got this from the maillog. Doesn't the "from=<...."
indicate
the envelope address? Here's a snippet of the error in the maillog:
Yes. It was not clear if you were referring to the syslog entry, or the
From: header.
Ok, so at least the envelope header is correct. So any clue as to why the
destination server would think this is a multi-recipient bounce message?
Again, this is the error I got...
May 30 07:32:46 server2 courieresmtp:
id=02044427.429B0721.00004F5E,from=<owne...@listas.americasnet.com>,addr=<magl...@uol.com.br>:
550 <magl...@uol.com.br>: Recipient address rejected: Multi-recipient
bounce
What would constitute an error like this?
The only one who can give you an answer to this question would be that
server's admin.
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.
It's rather unlikely that majordomo would specify NOTIFY=NONE.
13 messages in net.sourceforge.lists.courier-usersRe: [courier-users] multi-recipient b...
