Re: [courier-users] multi-recipient bounce (re-post)

[Sam Varshavchik]

Ricardo Kleemann writes:

Thanks Sam.

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?

The logs show that the envelope return address is not null.

Even though the log does show that, is it possible that courier is still
using a null envelope sender? I'm getting this same error from more than one
domain server. I'm assuming courier is providing multiple recipients in the
transaction, because this is happening with domains that have multiple
addresses in the alias include file. I've emailed the administrator to try
and see what the error is but I've received no reply.

Does courier use null envelope sender when delivering to addresses that are
members of an alias? If so, is there any way to get around that?

Bottom line is I think that majordomo simply does not work with Courier.

What's happening is that messages sent to an alias will have DSN NOTIFY=NONE set. If I send mail to a role address, and the sysadmin screwed up the alias forward, it's not my problem if the address bounces. If the message goes to the remote server which implements ESMTP DSN, everything's fine. If the remote server does not support the ESMTP DSN extension, Courier will use a null return address, in order to suppress the bounce.

pgp4DAq8jwIIT.pgp
Description: PGP signature