From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/21159 Path: main.gmane.org!not-for-mail From: Matt Pharr Newsgroups: gmane.emacs.gnus.general Subject: Message Forwarding (Re: Pterodactyl Gnus v0.76 is released) Date: 11 Feb 1999 16:03:17 -0800 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 1035159319 21581 80.91.224.250 (21 Oct 2002 00:15:19 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 00:15:19 +0000 (UTC) Cc: bugs@gnus.org Return-Path: Original-Received: from spinoza.math.uh.edu (spinoza.math.uh.edu [129.7.128.18]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id TAA15930 for ; Thu, 11 Feb 1999 19:04:42 -0500 (EST) 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 SAB23402; Thu, 11 Feb 1999 18:03:09 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Thu, 11 Feb 1999 18:03:57 -0600 (CST) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id SAA09534 for ; Thu, 11 Feb 1999 18:03:49 -0600 (CST) Original-Received: from lux.Stanford.EDU (lux.Stanford.EDU [171.64.77.150]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id TAA15909; Thu, 11 Feb 1999 19:03:40 -0500 (EST) Original-Received: (from mmp@localhost) by lux.Stanford.EDU (8.9.0/8.9.0) id QAA14666; Thu, 11 Feb 1999 16:03:18 -0800 (PST) Original-To: ding@gnus.org X-Face: C!.oGaE]n@p)VF9Ss3]f'|<)kRrtpG)^^b^X-3_zhUHp\jBj29jaoTItqWR>mHa+v-{/!jx7OA@!cV0>Fm-b:zEL<`oOXG[BFQ\ (message-forward): Use MIME. Another bug with this: read one message, hit c-c c-f to make a new forwarded message but don't send it. Then go back to the summary buffer and read another message. Hit c-c c-f to forward that one. When the first forwarded message is actually sent, the text of the second forwarded message will be included, rather than the intended text. > (message-included-forward-headers): Removed. I can understand that this is the right thing to do in that if one is going to forward a message, the whole thing should just be sent. But (for me at least) the more common case is that whoever I'm forwarding something on to is going to be unhappy to get all of those Received headers, etc. So do both of these together suggest that it would be better to inline the message immediately, with appropriate MML stuff around it (which would allow manual header pruning, at least). Is that possible in MML? -matt -- Matt Pharr mmp@graphics.stanford.edu