Re: [Mailman-Developers] Feature request: Reply-To Munging etc.

2007-03-10 Thread Dan MacNeil
> Dan MacNeil writes: > > For my selfish purposes, "no-dupes" off is a better default setting. > > Without a copy of the message to their mailbox, many of my users will > > keep sending the same message because it "didn't go". Stephen J. Turnbull wrote: > Are you thinking of not-metoo? Err, ye

Re: [Mailman-Developers] Feature request: Reply-To Munging etc.

2007-03-10 Thread Sven Anderson
Barry Warsaw wrote: > I think you're both right :). Mailman 2.1 will strip recipients from > the CC header if explicitly named recipients are members of the list and > have nodup set. But Mailman won't strip To headers, nor juggle CC and > To headers after stripping. Is see. But wouldn't it b

Re: [Mailman-Developers] Feature request: Reply-To Munging etc.

2007-03-09 Thread Stephen J. Turnbull
Mark Sapiro writes: > I think Dan must be thinking of not-metoo, but note that even ensuring > that not-metoo is off won't do the job for gmail users thanks to > gmail's 'feature' of not showing 'duplicate' messages. Yeah, but that's irrelevant to use of no-dupes, because gmail is keying off a

Re: [Mailman-Developers] Feature request: Reply-To Munging etc.

2007-03-09 Thread Mark Sapiro
Stephen J. Turnbull wrote: >Dan MacNeil writes: > > > Stephen J. Turnbull quoted out of context: > > > I see your point, but why won't my suggestion of defaulting the per > > > user no-dupes to "on" do fine from that point of view? > > > For my selfish purposes, "no-dupes" off is a better default

Re: [Mailman-Developers] Feature request: Reply-To Munging etc.

2007-03-09 Thread Dan MacNeil
Stephen J. Turnbull quoted out of context: > I see your point, but why won't my suggestion of defaulting the per > user no-dupes to "on" do fine from that point of view? For my selfish purposes, "no-dupes" off is a better default setting. Without a copy of the message to their mailbox, many of my

Re: [Mailman-Developers] Feature request: Reply-To Munging etc.

2007-03-09 Thread Stephen J. Turnbull
Dan MacNeil writes: > Stephen J. Turnbull quoted out of context: > > I see your point, but why won't my suggestion of defaulting the per > > user no-dupes to "on" do fine from that point of view? > For my selfish purposes, "no-dupes" off is a better default setting. > Without a copy of the m

Re: [Mailman-Developers] Feature request: Reply-To Munging etc.

2007-03-09 Thread Stephen J. Turnbull
Barry Warsaw writes: > I think you're both right :). Mailman 2.1 will strip recipients from > the CC header if explicitly named recipients are members of the list > and have nodup set. But Mailman won't strip To headers, nor juggle > CC and To headers after stripping. Ah, right. I ra

Re: [Mailman-Developers] Feature request: Reply-To Munging etc.

2007-03-08 Thread Barry Warsaw
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mar 7, 2007, at 12:30 PM, Stephen J. Turnbull wrote: > Sven Anderson writes: > >>> IIRC, if the user sets their subscription to "no-dupes", that user's >>> address will be removed from the addressee list, as well as from the >>> list of addresses t

Re: [Mailman-Developers] Feature request: Reply-To Munging etc.

2007-03-08 Thread Sven Anderson
Stephen J. Turnbull, 07.03.2007 18:30: > Sven Anderson writes: > > > > IIRC, if the user sets their subscription to "no-dupes", that user's > > > address will be removed from the addressee list, as well as from the > > > list of addresses that Mailman actually distributes to the post to. > >

Re: [Mailman-Developers] Feature request: Reply-To Munging etc.

2007-03-07 Thread Stephen J. Turnbull
Sven Anderson writes: > > IIRC, if the user sets their subscription to "no-dupes", that user's > > address will be removed from the addressee list, as well as from the > > list of addresses that Mailman actually distributes to the post to. > > I just checked this to be sure, but only the lat

Re: [Mailman-Developers] Feature request: Reply-To Munging etc.

2007-03-06 Thread Sven Anderson
Stephen J. Turnbull, 06.03.2007 08:25: > Sven Anderson writes: > > > 1) Receiver clean-up (if Reply-To munging is NOT used) > > So what about an option to clean-up the receivers list in Mailman, > > that is Mailman removes all To/CC addresses which are members of > > the list? > > IIRC, if th

[Mailman-Developers] Feature request: Reply-To Munging etc.

2007-03-05 Thread Stephen J. Turnbull
Sven Anderson writes: > 1) Receiver clean-up (if Reply-To munging is NOT used) > So what about an option to clean-up the receivers list in Mailman, > that is Mailman removes all To/CC addresses which are members of > the list? IIRC, if the user sets their subscription to "no-dupes", that user

Re: [Mailman-Developers] Feature request: Reply-To Munging etc.

2007-03-05 Thread Jan-Benedict Glaw
On Mon, 2007-03-05 03:24:33 +0100, Sven Anderson <[EMAIL PROTECTED]> wrote: > 1) Receiver clean-up (if Reply-To munging is NOT used) > One of the problems not using Reply-To munging is, that by using the > reply-to-all function of MUAs the list of receivers tends to accumulate. As > in open lists

[Mailman-Developers] Feature request: Reply-To Munging etc.

2007-03-04 Thread Sven Anderson
Hi, as many of you probably would agree, whether you munge the Reply-To headers or not, both ways are not perfect. Just today I had a hard time again, as I'm not happy with both options, and finally came up with some ideas how the situation could be improved, about which I would like to read yo