From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/34725 Path: main.gmane.org!not-for-mail From: prj@po.cwru.edu (Paul Jarc) Newsgroups: gmane.emacs.gnus.general Subject: Re: Mail-Followup-To interaction with gnus-summary-followup Date: 11 Feb 2001 14:38:49 -0500 Sender: owner-ding@hpc.uh.edu Message-ID: References: <87y9vdwabb.fsf@sto-kerrig.org> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035170597 31839 80.91.224.250 (21 Oct 2002 03:23:17 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:23:17 +0000 (UTC) Cc: ding@gnus.org Return-Path: Original-Received: from karazm.math.uh.edu (karazm.math.uh.edu [129.7.128.1]) by mailhost.sclp.com (Postfix) with ESMTP id 5C63BD049D for ; Sun, 11 Feb 2001 14:39:30 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by karazm.math.uh.edu (8.9.3/8.9.3) with ESMTP id NAC04730; Sun, 11 Feb 2001 13:39:24 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Sun, 11 Feb 2001 13:38:35 -0600 (CST) Original-Received: from mailhost.sclp.com (postfix@66-209.196.61.interliant.com [209.196.61.66] (may be forged)) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id NAA13486 for ; Sun, 11 Feb 2001 13:38:23 -0600 (CST) Original-Received: from multivac.cwru.edu (multivac.STUDENT.CWRU.Edu [129.22.96.25]) by mailhost.sclp.com (Postfix) with SMTP id A6749D049D for ; Sun, 11 Feb 2001 14:38:51 -0500 (EST) Original-Received: (qmail 6506 invoked by uid 500); 11 Feb 2001 19:39:11 -0000 Mail-Followup-To: ding@gnus.org, sneakums@sto-kerrig.org Original-To: Paul J Collins In-Reply-To: Paul J Collins's message of "11 Feb 2001 14:42:22 +0000" User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 Precedence: list X-Majordomo: 1.94.jlt7 Original-Lines: 41 Xref: main.gmane.org gmane.emacs.gnus.general:34725 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:34725 Paul J Collins writes: > I'm unsure of the semantics of Mail-Followup-To, > I'm on a mailing list that I filter into a separate group, and one of > the posters has a Mail-Followup-To header with the list's address in > it. I had already set the group's parameters for to-list and > to-address to the address of list. I think having to-address makes to-list unnecessary. > When I type `f' to follow up to this person's posts, my new message is > given a To field with the value of to-address, and a Cc field with the > value of the original poster's Mail-Followup-To. What is the value of message-use-followup-to? > I want to disable this behaviour. Honouring Mail-Followup-To in the > case where the mail is already going to that address doesn't make > much sense to me. I think to-address is intended for a world without Mail-Followup-To, and vice versa. If the message you're following up to already tells you where the followup should go, you don't need to-address. Since you can edit the addresses in the message either way, I think it's best to prefer Mail-Followup-To (per-message, more specific) over to-address (per-group, more general). So message.el should be changed around 19 lines into message-get-reply-headers: (if (or (not wide) to-address) should be: (if (and (not mft) (or (not wide) to-address)) You can blame me for this, BTW. I wrote the MFT code, but didn't quite understand to-address at the time, I guess. paul