Re: [Mailman-Developers] feature request: new option for reply_goes_to_list
[I hope you don't mind that I redirect this to the list, I think I have a suggestion to improve mailman 2.1
On Sun, Sep 08, 2002 at 06:31:28PM -0700, Peter C. Norton wrote:
BTW, the reason that I set reply-to's on one of the lists I run is that when a thread gets going and lots of people start responding, for some reason the Cc: list grew as long as my arm. And I got really
That's indeed a minor problem, but at least with the nodupes feature in mailman 2.1, you only get one copy.
Now that I think of it, it wouldn't be too hard for mailman when it sends the list copy out to (optionally) remove from Cc all the Emails from members that have the nodupes option set. That way, the Cc would be left only with Emails that aren't subscribed to the list.
What do you think?
Though many people know better, my experience even on a somewhat technical list is that most people don't exercise any discipline in discriminating who they reply to, and they assume that the list is going to work with their mailer and dtrt. So I work with that assumption.
Unfortunately you aren't the only one. Am I so deluted to still want people to learn and know just a tiny little bit about their mail clients and use them properly?
Note that I'm not just bitching, I did spend many hours writing a patch to do reply-to munging per receipient so that people who really aren't willing to learn and/or bitch too loudly can be given the option just for them and then they leave you in peace (announced here a few months ago, and an outdated copy is here: http://mail.python.org/pipermail/mailman-users/2002-March/018145.html http://mail.python.org/pipermail-21/mailman-developers/2002-March/011068.htm... http://marc.merlins.org/tmp/replyto.diff.cvs )
Unfortunately it never made the cut for mailman 2.1
Marc
"A mouse is a device used to point at the xterm you want to type in" - A.S.R. 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 Sun, Sep 08, 2002 at 06:52:17PM -0700, Marc MERLIN wrote:
[I hope you don't mind that I redirect this to the list, I think I have a suggestion to improve mailman 2.1
On Sun, Sep 08, 2002 at 06:31:28PM -0700, Peter C. Norton wrote:
BTW, the reason that I set reply-to's on one of the lists I run is that when a thread gets going and lots of people start responding, for some reason the Cc: list grew as long as my arm. And I got really
That's indeed a minor problem, but at least with the nodupes feature in mailman 2.1, you only get one copy.
Now that I think of it, it wouldn't be too hard for mailman when it sends the list copy out to (optionally) remove from Cc all the Emails from members that have the nodupes option set. That way, the Cc would be left only with Emails that aren't subscribed to the list.
What do you think?
That would definetly limit the # of Cc:'s on a message. Its an interesting approach, though perhaps too subtle. I think it would be appropriate to also have an option that just stripped Cc's.
Though many people know better, my experience even on a somewhat technical list is that most people don't exercise any discipline in discriminating who they reply to, and they assume that the list is going to work with their mailer and dtrt. So I work with that assumption.
Unfortunately you aren't the only one. Am I so deluted to still want people to learn and know just a tiny little bit about their mail clients and use them properly?
Marc, I noticed that I got 2 of these messages in my inbox. Even though you know I'm subscribed to mailman-developers, you sent me a copy. This is the thing that I use reply-to forcing to prevent. I suspect you did this on purpose, so I'd like to hear whave you had in mind when you sent this.
Note that I'm not just bitching, I did spend many hours writing a patch to do reply-to munging per receipient so that people who really aren't willing to learn and/or bitch too loudly can be given the option just for them and then they leave you in peace (announced here a few months ago, and an outdated copy is here: http://mail.python.org/pipermail/mailman-users/2002-March/018145.html http://mail.python.org/pipermail-21/mailman-developers/2002-March/011068.htm... http://marc.merlins.org/tmp/replyto.diff.cvs )
Unfortunately it never made the cut for mailman 2.1
I know how you feel. I'm going to have to apply my patch to automaticly reject messages from addresses that aren't subscribed to 2.0.x. I wish I could have written it before 2.0 came out. On the positive side I know a lot more about python now, and maybe I can update my patch to use withlist to make old lists behave the right way, and to remove the stuff I put in for 2.x where x > 0.
-Peter
-- The 5 year plan: In five years we'll make up another plan. Or just re-use this one.
On Sun, Sep 08, 2002 at 09:42:08PM -0700, Peter C. Norton wrote:
Now that I think of it, it wouldn't be too hard for mailman when it sends the list copy out to (optionally) remove from Cc all the Emails from members that have the nodupes option set. That way, the Cc would be left only with Emails that aren't subscribed to the list.
What do you think?
That would definetly limit the # of Cc:'s on a message. Its an interesting approach, though perhaps too subtle. I think it would be appropriate to also have an option that just stripped Cc's.
That wouldn't work too well I think, if I post to a list and Cc a non subscriber on purpose, the non subscriber will not get the replies (although admittedly, he won't get them either if people use list reply instead of group reply)
Unfortunately you aren't the only one. Am I so deluted to still want people to learn and know just a tiny little bit about their mail clients and use them properly?
Marc, I noticed that I got 2 of these messages in my inbox. Even though you know I'm subscribed to mailman-developers, you sent me a copy. This
I usually use group reply instead of list-reply because of the above reason. The other reason is that if you are Cced in the answer, you see I answered your post and you can sort the mail in a way that you'll read it earlier.
I didn't see your answer because I wasn't Cced, and it could have sat in my random list mail folder for quite a while before I saw it.
But since you requested it (people usually but it in the header or footer), I used list reply on this answer.
is the thing that I use reply-to forcing to prevent. I suspect you did
Well, you are behind the times :) Ben and I got code in mailman 2.1 (which runs this list) that lets you not get the second copy. You just didn't enable the option. Go to http://mail.python.org/mailman-21/options/mailman-developers and check "Avoid duplicate copies of messages?"
Besides reply-to munging in no way prevents you from getting a copy: group reply will reply to the reply-to address + To + Cc, so everyone gets a copy anyway.
Marc
"A mouse is a device used to point at the xterm you want to type in" - A.S.R. 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)
-
Marc MERLIN -
Peter C. Norton