Fwd: Amway Order Confirmation [#1095286]
I get these messages from a particular sender who must have set his message to urgent. I have no influence over how these messages are sent. What must I do to my Mailman list, so the messages go through as originally sent and not in the form shown below?
As it is, Mailman does not attach the original message.
On 02/17/2017 01:32 PM, Dominik Hoffmann wrote:
I get these messages from a particular sender who must have set his message to urgent. I have no influence over how these messages are sent. What must I do to my Mailman list, so the messages go through as originally sent and not in the form shown below?
Mailman has a feature for 'urgent' messages. If an incoming message has an
Urgent: xxx
header where xxx is one of the list admin, moderator or poster passwords, the message is sent immediately to all list members regardless of regular/digest or delivery enabled/disabled status
If the password doesn't match one of the three list passwords, the message is rejected rather than accepted as a normal message so that the sender knows it wasn't delivered as an urgent message.
If you can't prevent the message from being posted with an Urgent: header, you can change Mailman's behavior from reject to accept as normal.
To do this, you need to patch Mailman/Handlers/CalcRecips.py. Around line 58 there is a comment:
Remove that comment and the following 21 lines that end with:
As it is, Mailman does not attach the original message.
I suspect the attachment of the original message is lost when the user forwards the reject to you because it certainly should be attached to the rejection notice.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 02/17/2017 01:32 PM, Dominik Hoffmann wrote:
I get these messages from a particular sender who must have set his message to urgent. I have no influence over how these messages are sent. What must I do to my Mailman list, so the messages go through as originally sent and not in the form shown below?
I may have missed this in my original reply. Are you saying that the message below came from the list? If so, then what is happening is the user is posting something with an Urgent: header. It is rejected by Mailman and the user then forwards the rejection notice back to the list, this time without an Urgent: header.
The original is not attached either because the user's MUA doesn't include it in the forwarded message or your list's content filtering doesn't accept message/rfc822 MIME parts.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 02/17/2017 10:17 PM, Dominik Hoffmann wrote:
How would I instruct the list to treat urgent messages like any other?
Se my first reply at <https://mail.python.org/pipermail/mailman-users/2017-February/081930.html> which tells you how to modify Mailman/Handlers/CalcRecips.py to ignore Urgent: headers.
If you don't have access to the Mailman code on the Mailman server that supports your list, the answer is you can't. This is not a configuration option. It can only be done by modifying the Mailman code.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 02/17/2017 01:32 PM, Dominik Hoffmann wrote:
I get these messages from a particular sender who must have set his message to urgent. I have no influence over how these messages are sent. What must I do to my Mailman list, so the messages go through as originally sent and not in the form shown below?
Mailman has a feature for 'urgent' messages. If an incoming message has an
Urgent: xxx
header where xxx is one of the list admin, moderator or poster passwords, the message is sent immediately to all list members regardless of regular/digest or delivery enabled/disabled status
If the password doesn't match one of the three list passwords, the message is rejected rather than accepted as a normal message so that the sender knows it wasn't delivered as an urgent message.
If you can't prevent the message from being posted with an Urgent: header, you can change Mailman's behavior from reject to accept as normal.
To do this, you need to patch Mailman/Handlers/CalcRecips.py. Around line 58 there is a comment:
Remove that comment and the following 21 lines that end with:
As it is, Mailman does not attach the original message.
I suspect the attachment of the original message is lost when the user forwards the reject to you because it certainly should be attached to the rejection notice.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 02/17/2017 01:32 PM, Dominik Hoffmann wrote:
I get these messages from a particular sender who must have set his message to urgent. I have no influence over how these messages are sent. What must I do to my Mailman list, so the messages go through as originally sent and not in the form shown below?
I may have missed this in my original reply. Are you saying that the message below came from the list? If so, then what is happening is the user is posting something with an Urgent: header. It is rejected by Mailman and the user then forwards the rejection notice back to the list, this time without an Urgent: header.
The original is not attached either because the user's MUA doesn't include it in the forwarded message or your list's content filtering doesn't accept message/rfc822 MIME parts.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 02/17/2017 10:17 PM, Dominik Hoffmann wrote:
How would I instruct the list to treat urgent messages like any other?
Se my first reply at <https://mail.python.org/pipermail/mailman-users/2017-February/081930.html> which tells you how to modify Mailman/Handlers/CalcRecips.py to ignore Urgent: headers.
If you don't have access to the Mailman code on the Mailman server that supports your list, the answer is you can't. This is not a configuration option. It can only be done by modifying the Mailman code.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Dominik Hoffmann -
Mark Sapiro