Manually bouncing messages to a mailman list
Hi list. Here's an interesting (at least for me :) mailman problem that I could not manage to solve.
If I manually bounce messages to a mailman list (I mean: using the "bounce" command in mutt, or the "mail redirect" thunderbird plugin), the messages seems to disappear:
they don't get delivered to the list (as I would expect when the original sender address is subscribed to the list)
they don't go into the moderation queue (as I would expect when the original sender address is not subscribed to the list)
they don't bounce back to the original sender (nor to the address who bounced the message to the list, nor to the list administrator)
Please note that I am a subscriber (and administrator) of the list in question, but I don't have shell access to the server running mailman (version 2.1.9), so I can't debug the problem myself.
Could it be that the "Resent-*" headers that get added to the bounced message are somehow confusing mailman? Or is this a feature? Or a mis-configuration?
I couldn't find anything relevant in the list archives and the documentation, except for this page, which mentions manually bouncing messages to a list:
http://wiki.list.org/pages/viewpage.action?pageId=4030683
I tried following the procedure described in that page (i.e. including an "Approved: " header with the admin password) but the result is still the same.
Any ideas?
Cri
-- GPG/PGP Key-Id 0x943A5F0E - http://www.linux.it/~cri/cri.asc
Cristian Rigamonti wrote:
If I manually bounce messages to a mailman list (I mean: using the "bounce" command in mutt, or the "mail redirect" thunderbird plugin), the messages seems to disappear:
<snip>
Could it be that the "Resent-*" headers that get added to the bounced message are somehow confusing mailman? Or is this a feature? Or a mis-configuration?
It's not the added headers. It's the X-BeenThere: header in the original message. You have to remove it.
There is a "Discarded message" entry in Mailman's vette log, but since you don't have access, you can't see it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sat, Aug 09, 2008 at 07:50:34AM -0700, Mark Sapiro wrote:
It's not the added headers. It's the X-BeenThere: header in the original
message. You have to remove it.
Uhm, I've checked both the original message and the bounced message (going out of my mutt), and neither contains the "X-BeenThere: " header. The only difference is the Resent-* headers (mutt also strips the "Delivered-To: " header from bounced messages).
Let me clarify the scenario:
- Somebody sends me a message
- I think the message should really go to the list, not to me
- I bounce the message to the list (if the original sender is not subscribed to the list I expect to find it in the moderation queue)
- The message disappears
There is a "Discarded message" entry in Mailman's vette log, but since
you don't have access, you can't see it.
Thanks, I'll ask the sysadmin to have a look at that.
Cri
-- GPG/PGP Key-Id 0x943A5F0E - http://www.linux.it/~cri/cri.asc
Cristian Rigamonti wrote:
On Sat, Aug 09, 2008 at 07:50:34AM -0700, Mark Sapiro wrote:
It's not the added headers. It's the X-BeenThere: header in the original message. You have to remove it.
Uhm, I've checked both the original message and the bounced message (going out of my mutt), and neither contains the "X-BeenThere: " header. The only difference is the Resent-* headers (mutt also strips the "Delivered-To: " header from bounced messages).
Sorry, I misunderstood.
Let me clarify the scenario: the list I expect to find it in the moderation queue)
- Somebody sends me a message
- I think the message should really go to the list, not to me
- I bounce the message to the list (if the original sender is not subscribed to
Maybe not. If you are a member and the envelope of the bounced message is from you, it will be considered a post from you.
- The message disappears
There is a "Discarded message" entry in Mailman's vette log, but since you don't have access, you can't see it.
Thanks, I'll ask the sysadmin to have a look at that.
The message won't be too helpful in this situation. It just says 'Message discarded, msgid: ...', but if it is present, it will verify that the message reached Mailman and Mailman discarded it for some reason.
I don't yet understand why Mailman would discard the message, but I am able to duplicate the problem, so I will investigate further tomorrow.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Aug 13, 2008 at 08:33:14AM -0700, Mark Sapiro wrote:
Let me clarify the scenario: the list I expect to find it in the moderation queue)
- Somebody sends me a message
- I think the message should really go to the list, not to me
- I bounce the message to the list (if the original sender is not subscribed to
Maybe not. If you are a member and the envelope of the bounced message is from you, it will be considered a post from you.
I thought about that, so I tested both possibilities for the envelope sender of the bounced message: envelope from me (yes, I am a member of the list) or envelope from the sender of the original message (I tested both cases: member or not-member of the list); in all tests the message disappears.
There is a "Discarded message" entry in Mailman's vette log, but since you don't have access, you can't see it.
Thanks, I'll ask the sysadmin to have a look at that.
The message won't be too helpful in this situation. It just says 'Message discarded, msgid: ...', but if it is present, it will verify that the message reached Mailman and Mailman discarded it for some reason.
I got feedback from the sysadm: indeed the message is discarded by mailman:
Aug 12 13:43:44 2008 (6025) Message discarded, msgid: <20080720101847.GA4783@pegasus>
I don't yet understand why Mailman would discard the message, but I am able to duplicate the problem, so I will investigate further tomorrow.
Thank you very much! Let me know if I can help you somehow (reminder: I'm using mailman version 2.1.9)
Cri
-- GPG/PGP Key-Id 0x943A5F0E - http://www.linux.it/~cri/cri.asc
Cristian Rigamonti wrote:
On Wed, Aug 13, 2008 at 08:33:14AM -0700, Mark Sapiro wrote:
I don't yet understand why Mailman would discard the message, but I am able to duplicate the problem, so I will investigate further tomorrow.
Thank you very much! Let me know if I can help you somehow (reminder: I'm using mailman version 2.1.9)
It turns out I was mistaken. I can't duplicate the problem. I only thought I could because the test list I was using had generic_nonmember_action set to Discard. When I set that to Hold, the mutt bounced message is held as expected.
If you are sure that you don't have some list setting like the above that's causing this, you can bounce a message to both the list and to me <mark@msapiro.net>, and I'll look at it further. If you do this, also send me an email from you so I don't just ignore the 'bounced' email as spam.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Thu, Aug 14, 2008 at 10:41:29AM -0700, Mark Sapiro wrote:
It turns out I was mistaken. I can't duplicate the problem. I only thought I could because the test list I was using had generic_nonmember_action set to Discard. When I set that to Hold, the mutt bounced message is held as expected.
Sorry folks, I finally tracked down a mis-configuration on my side.
A spam filter rule contained the (hungry) regexp
X-Spam-Status:.*YES
instead of the more reasonable
X-Spam-Status: YES
The messages I tried to bounce had this header:
X-Spam-Status: No, score=-2.5 required=3.0 tests=BAYES_00,RDNS_NONE...
which (blame BAYES :-) matches the regexp, so the message got discarded.
Cri
-- GPG/PGP Key-Id 0x943A5F0E - http://www.linux.it/~cri/cri.asc
participants (2)
-
Cristian Rigamonti -
Mark Sapiro