New option for mailman-cvs: reply-to munging per user
Ok, so my plan was to make listwide reply-to munging go away (well, it would still be there, but hopefully not needed in most cases/installations).
Two things were needed for that:
- no dupe patch written by Ben and already in mailman cvs thanks to Barry
- for really whiney users who just don't want to use reply to all to reply to a list post and who are not going to leave you alone (kind of defies logic, but this is a topic where logic does not apply), I spent the last evenings writing a new setting: reply-to munging per user and per list
Per Barry's recommendation, I wrote this by adding a flag for each user and duping each list message (munged and non munged version) and sending the right version to each user. Since this adds some processing, I added an optimization to bypass this code if no one on the list requests munging.
Munging per user is both a setting that is system wide, and if it's allowed, it can be allowed listwide (system wide defaults to yes, list wide to no). I've also made normal listwide reply-to munging a system wide option that can be turned off.
Note that this code is functional, but still has a couple of rough edges
- I didn't give is as much testing as I would have liked (I just finished it and I need to get a little sleep before I go to work :-D)
- It is missing the code to disable split munge/no munge processing if the last munge user goes back to nomunge Actually, I just thought about doing this by setting mixed_reply_to_munging_users back to 0 if after scanning the list at sending time, we find out that one of the two posts isn't being sent to anyone. (And I'll also have to deal with the pathological case where all the list users set themselves to munging)
- It still has some debugging code in there
I'm simply posting this right now because I'd like to get feedback from you and Barry on the implementation and python details before I send a polished patch to Barry for his consideration.
Marc
Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key
On Mon, 11 Mar 2002, Marc MERLIN wrote:
- no dupe patch written by Ben and already in mailman cvs thanks to Barry
Just wanted to note that one big piece of this (which is currently left out) still causes other problems. The crossposted message is still recieved multiple times, and even if some data managing system to track deliveries and get it right is built into mailman, that system probably wouldn't work with the smurf army scalability solution. Are there any other elements hiding anywhere that similarly cause the army problems?
-Dale
On Mon, Mar 11, 2002 at 05:56:36AM -0500, Dale Newfield wrote:
On Mon, 11 Mar 2002, Marc MERLIN wrote:
- no dupe patch written by Ben and already in mailman cvs thanks to Barry
Just wanted to note that one big piece of this (which is currently left out) still causes other problems. The crossposted message is still recieved multiple times, and even if some data managing system to track
Yes, that's known. The piece of code that did that had a tendency to keep using memory until you killed the qrunner. Barry did not include it as a result (Ben is working on rewriting that piece of code in a way that doesn't keep eating memory) It is however possible to add the code back from the original updated patch I posted and restart qrunner nightly to free up the memory.
deliveries and get it right is built into mailman, that system probably wouldn't work with the smurf army scalability solution. Are there any other elements hiding anywhere that similarly cause the army problems?
nodupes is a per end user feature (enabled by default for new users). It is true that if you forge a Cc in an Email before you send it to the MLM, it will cause that end user to not receive a list ocpy.
- There isn't much that can be done about that.
- It will not be an issue in most cases
- end users worried by this can definitely turn nodupes off (and do deduping with procmail or some such)
nodupes was a feature already present in a few advanced MLMs and at least Ben and I saw it as a much needed feature for mailman
Marc
Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key
participants (2)
-
Dale Newfield
-
Marc MERLIN