[ mailman-Patches-644129 ] Edit held message header/body
Patches item #644129, was opened at 2002-11-26 14:44 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644129&group_id=103
Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: anser (anser) Assigned to: Nobody/Anonymous (nobody) Summary: Edit held message header/body
Initial Comment: Here is my preliminary (brute force) patch to allow full editing of headers and bodies of messages being held for approval in Mailman 2.1 (as of beta 5). I have released versions of this for 1.x and 2.0.x but wanted to wait until 2.1 was fairly stable before releasing this one.
You must set HOLD_MESSAGES_AS_PICKLES = 0 in your installation's mm_cfg.py for this to work. I may support pickles in a future version. Personally I don't see that much performance difference anyway, not on the held stuff... Also note that if you had HOLD_MESSAGES_AS_PICKLES = 1 (the default) when you created a list, you must recreate it after changing that variable. (Learned the hard way)
This patch overrides the ADMINDB_PAGE_TEXT_LIMIT setting, so if you have megabyte messages being held, be ready to wait.
Also - this version doesn't change the request database, so if you change the Subject: header you won't see the change reflected in the summary list (but it will be sent out your way when you Approve).
Happy mailmanning!
Comment By: anser (anser) Date: 2002-11-27 16:40
Message: Logged In: YES user_id=49958
The problem with moving this to 2.2/3.0 is that I actually have no way of knowing whether it will work with 2.2/3.0 - it is based on 2.1. I actually don't expect this feature to ever be folder into "official" Mailman since editing the envelope is apparently considered heresy :) but I want the patch to be available for people who need it. Just so it stops moving so I can post the URL...
Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 14:04
Message: Logged In: YES user_id=12800
I'm moving this to the 2.2/3.0 group since we're in feature freeze for 2.1
You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=644129&group_id=103
participants (1)
-
noreply@sourceforge.net