From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/37334 Path: main.gmane.org!not-for-mail From: Karl Kleinpaste Newsgroups: gmane.emacs.gnus.general Subject: Re: Request: ding subscribers' group parameter Date: Tue, 31 Jul 2001 17:37:27 -0400 Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1035172767 13320 80.91.224.250 (21 Oct 2002 03:59:27 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:59:27 +0000 (UTC) Keywords: to-address,parameters,list,group,feature Return-Path: Return-Path: Original-Received: (qmail 28093 invoked from network); 31 Jul 2001 21:37:30 -0000 Original-Received: from mesquite.slip.cs.cmu.edu (HELO cinnamon.vanillaknot.com) (128.2.207.11) by gnus.org with SMTP; 31 Jul 2001 21:37:30 -0000 Original-Received: (from karl@localhost) by cinnamon.vanillaknot.com (8.11.2/8.11.2) id f6VLbSV31027; Tue, 31 Jul 2001 17:37:28 -0400 Original-To: ding@gnus.org X-Face: ?=p^Gj2JkX~UU_@W}[q/'Dxn19x-zfIQ](y<&ky/?1-&Nz&,!W}R.Gp+"LeGojoR =RF>?!XVs{a:`Yt(gqM<#$Zy(C@]'dR4Hy4S1.I(n3:2"R:=Uy!)K9>U!gNTyH{p +_w#F[gt).$Vyvo5=9LF^PeQ(@H#}QLAbfyYxX/8t:TDR5nA\|RmJO"EwjL8tWyvM Mail-Followup-To: set-the-damn--to-address--in-group-parameters@[127.0.0.1] In-Reply-To: (prj@po.cwru.edu's message of "Tue, 31 Jul 2001 12:15:23 -0400") User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.4 (Artificial Intelligence) Original-Lines: 62 Xref: main.gmane.org gmane.emacs.gnus.general:37334 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:37334 prj@po.cwru.edu (Paul Jarc) writes: > Since Gnus now respects Mail-Followup-To, it'd be better to encourage > people to add that field to outgoing messages. Let me see if I've got this straight: Gnus provides a feature explicitly designed¹ to eliminate duplicate copies to individuals inhabiting mailing lists. This feature works every single time, in every single instance, if only the list subscribers will deploy it as intended. Yet we should ignore this feature, instead in favor of Yet Another Header. Right. Just checking. > I think the best way > to do this would be to look at the current group's parameters; if > there is a to-address or to-list parameter and its address is included > in To+Cc, then we should generate MFT. "If there is a to-address" in the group parameters...? If every ding subscriber would use to-address, then the point would be moot, as the problem would already be solved in the manner suggested. There is _no reason_ for any ding subscriber /not/ to be using to-address. I mean, the suggestion was merely to put this valuable Gnus property to use. You'd think that Gnus' own development crew would be the very *first* to put it to use, uniformly and correctly. It's a no-brainer, involving the sequence M-C-e ((to-address . "ding@gnus.org")) C-c C-c as you read this message, with minor modifications if you have to insert the to-address element into a set of other existing parameters. Instead of everyone just doing that, and the problem disappearing in the course of a single day, we now have a full-blown discussion over code changes in order to handle non-existent failure cases in what is already the default situation when the property is properly in use. Do I have that right? If you want to insert MFT headers, fine, but "to-address" provides exactly the feature you're looking for on *this* list, among *this* universe of subscribers. And the price of lunch says MFTs won't do a bit of good on yahoogroups mailing lists, where Joe Random Users from all over the planet are still using Outlook Express as packaged with Win98 which has no awareness of MFT at all. Solve the problems you can, where you can, as simply as you can. M-C-e ((to-address . "ding@gnus.org")) C-c C-c Do it. _*/Problem solved./*_ yes, i'm annoyed, --karl ¹ *Info* -> Gnus -> Group Buffer -> Group Parameters, "to-address": "This is primarily useful in mail groups that represent closed mailing lists--mailing lists where it's expected that everybody that writes to the mailing list is subscribed to it. Since using this parameter ensures that the mail only goes to the mailing list itself, it means that members won't receive two copies of your followups."