From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/32961 Path: main.gmane.org!not-for-mail From: prj@po.cwru.edu (Paul Jarc) Newsgroups: gmane.emacs.gnus.general Subject: Re: Mail-{Followup,Reply}-To Date: 24 Oct 2000 18:48:00 -0400 Sender: owner-ding@hpc.uh.edu Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035169156 22683 80.91.224.250 (21 Oct 2002 02:59:16 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 02:59:16 +0000 (UTC) Return-Path: Original-Received: from spinoza.math.uh.edu (spinoza.math.uh.edu [129.7.128.18]) by mailhost.sclp.com (Postfix) with ESMTP id D9BAED049A for ; Tue, 24 Oct 2000 18:52:17 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by spinoza.math.uh.edu (8.9.1/8.9.1) with ESMTP id RAB07615; Tue, 24 Oct 2000 17:48:51 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Tue, 24 Oct 2000 17:48:15 -0500 (CDT) 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 RAA27401 for ; Tue, 24 Oct 2000 17:48:02 -0500 (CDT) Original-Received: from multivac.student.cwru.edu (multivac.STUDENT.CWRU.Edu [129.22.239.69]) by mailhost.sclp.com (Postfix) with SMTP id 333ADD049A for ; Tue, 24 Oct 2000 18:48:24 -0400 (EDT) Original-Received: (qmail 1640 invoked by uid 500); 24 Oct 2000 22:48:22 -0000 Mail-Followup-To: ding@gnus.org Original-To: ding@gnus.org In-Reply-To: Per Abrahamsen's message of "24 Oct 2000 14:45:04 +0200" Original-Lines: 10 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:32961 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:32961 Per Abrahamsen writes: > I don't think it would be hard to teach message.el to obey the two > headers. It could also generate the two headers based on group > parameters. If "broken-reply-to" is set, generate "mail-reply-to". Is broken-reply-to currently used for anything? I wonder if this should be handled separately. paul