On 11/8/21 8:28 PM, dancab@caltech.edu wrote:
In either case, the bounce message (fake DSN) should have contained a message body like Mail to user@example.com failed at outgoing SMTP with the actual user's address. These fake DSNs are sent in the case where the outgoing MTA refuses a message from Mailman so there is no actual failure DSN.
Thanks. I think I'm missing how I can configure Mailman so that the actual user's address is used.
I think you are missing the point. This is a pseudo DSN. If it were a real DSN it would be something like
From: mailer-daemon@somewhere To: listname-bounces@listdomain
However, there is no real DSN because Mailman has gotten a reject in it's attempt to deliver to the outgoing MTA so it creates it's own pseudo DSN for the failure.
Another way of looking at this is if you configured Mailman to deliver to a local MTA and configured that MTA to relay to your remote MTA, your local MTA would accept the message and then receive the 5xx status upon delivery to the Remote MTA and would then send an appropriate DSN back to the list-bounces address.
Since you are skipping the local MTA part, Mailman gets the 5xx status upon delivery to the remote MTA and creates it's own DSN for itself.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan