
Dear Mailman Users Group,
I know I have a misconfiguration somewhere in my POSTFIX MTA, but am not sure where and was hoping someone could point me to the right documentation.
I have some users sending messages to lists of which they are subscribed to and they successfully deliver, but there are some email users deliveries that fail and that delivery status is sent back to them (the sender) rather than the MAILMAN list owner.
Can someone please advise what I need to do to properly return a delivery status notification to the MAILMAN List Owner to correct this problem? Thank you, Rose

Futchko, Rose wrote:
I have some users sending messages to lists of which they are subscribed to and they successfully deliver, but there are some email users deliveries that fail and that delivery status is sent back to them (the sender) rather than the MAILMAN list owner.
This is probably not something you can do anything about. Mailman sends messages with the envelope from LISTNAME-bounces@example.com, or if VERPed, LISTNAME-bounces+recipient=example.net@example.com. bounces (DSNs) should be returned to this address where they are processed by Mailman according to the list's bounce processing settings.
What you are seeing is some MTA in the delivery path to the recipient is returning a DSN to the poster (i.e. the address in a From: or perhaps Reply-To: header) rather than to the envelope sender. The misconfiguration or more likely, just plain brokenness, is in this MTA which serves the intended recipient and is probably not under your control. Short of reporting this to the admins of the MTA that generated the DSN, there's little if anything you can do.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Shapiro, Mark wrote:
What you are seeing is some MTA in the delivery path to the recipient is returning a DSN to the poster (i.e. the address in a From: or perhaps Reply-To: header) rather than to the envelope >sender. The misconfiguration or more likely, just plain brokenness, is in this MTA which serves the intended recipient and is probably not under your control.
Our organization owns the MTA and supports it internally. What should I tell the admin of the POSTFIX MTA to change or look for?

Futchko, Rose wrote:
Shapiro (sic), Mark wrote:
What you are seeing is some MTA in the delivery path to the recipient is returning a DSN to the poster (i.e. the address in a From: or perhaps Reply-To: header) rather than to the envelope >sender. The misconfiguration or more likely, just plain brokenness, is in this MTA which serves the intended recipient and is probably not under your control.=20
Our organization owns the MTA and supports it internally. What should I tell the admin of the POSTFIX MTA to change or look for?
I have never seen Postfix do this. As far as I know there is no way to misconfigure Postfix that would make it do this.
Are you certain that the DSNs your posters are receiving come from your organization's Postfix? More likely Mailman delivers to your Postfix which in turn delivers successfully to the remote domain's MX and that MTA then encounters a delivery problem and returns the DSN.
Look at all the headers of the errant DSN. Often it will be From: mailer-daemon@some.domain or something similar which may identify the MTA's domain. Also, the first Received: header (furthest from the top of the headers) will show the server the DSN came from.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Hello List, I have some lists set up that i essentially use as distribution lists to communicate with members of an amateur sporting club. I originally sent a message advising of an event on 22nd and 23rd September. Last night, I forwarded that message to the list as a reminder, but both the original message and the reminder message were received as attachments, 1 text document and 1 HTML document.
Is this normal? I don't believe that it has happened before.
Thanks very much in advance, Stewart.

Stewart Hamling wrote:
I have some lists set up that i essentially use as distribution lists to communicate with members of an amateur sporting club. I originally sent a message advising of an event on 22nd and 23rd September. Last night, I forwarded that message to the list as a reminder, but both the original message and the reminder message were received as attachments, 1 text document and 1 HTML document.
Is this normal? I don't believe that it has happened before.
There are many things possibly involved in this. The MUA used to compose the message and its settings and whether the forward was "inline" or "as attachment" affect the MIME structure of the message delivered to Mailman. Then Mailman's content filtering settings, the Mailman version and whether the list adds msg_header and/or msg_footer affect the MIME structure of the message sent from Mailman. Also, various agents along the way may add disclaimers or privacy notices to the message which may affect its MIME structure. Finally, the MUA used to view the message received from Mailman will affect how any particular MIME structure is rendered.
See the FAQ at <http://wiki.list.org/x/84A9> for some more on this.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Sapiro, Mark wrote:
Are you certain that the DSNs your posters are receiving come from your organization's Postfix? No, the response are coming from the destination DSN's.
More likely Mailman delivers to your Postfix which in turn delivers successfully to the remote domain's MX and that MTA then encounters a delivery problem and returns the DSN. This is correct and appears to be handling it properly.
How can I configure posted messages sent to only send errors back to the list owner or moderator? Some of the mail lists have over 2,000 participants, and do not want to flood valid posters mailboxes with messages that cannot be delivered.
Thank you, Rose

Futchko, Rose wrote:
Sapiro, Mark wrote:
Are you certain that the DSNs your posters are receiving come from your organization's Postfix?
No, the response are coming from the destination DSN's.
[...]
How can I configure posted messages sent to only send errors back to the list owner or moderator? Some of the mail lists have over 2,000 participants, and do not want to flood valid posters mailboxes with messages that cannot be delivered.
You can't. Mailman is already doing everything it can short of munging the From: address of posts to ensure that DSNs are returned to Mailman. In addition to setting the envelope sender of posts to the listname-bounces address, Mailman also puts the listname-bounces address in Sender: and Errors-To: headers in the post.
If in spite of all this and in violation of all standards, some remote MTA insists on returning a DSN to the From: address, there are really only two things you can do.
You can contact the admins of the MTA that sends the DSN and complain. This is probably futile.
You or another list admin can post fairly frequently to the list, and when you receive a DSN addressed to you, immediately remove the offending recipient from the list.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Futchko, Rose
-
Mark Sapiro
-
Stewart Hamling