From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/23462 Path: main.gmane.org!not-for-mail From: Karl Kleinpaste Newsgroups: gmane.emacs.gnus.general Subject: p0.88 misparses 2nd-level message forwarding Date: 22 Jun 1999 17:14:32 -0400 Sender: owner-ding@hpc.uh.edu Message-ID: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035161190 2125 80.91.224.250 (21 Oct 2002 00:46:30 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 00:46:30 +0000 (UTC) Keywords: message/rfc822,text/plain,level,containing,original,inline Return-Path: Original-Received: from farabi.math.uh.edu (farabi.math.uh.edu [129.7.128.57]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id RAA13674 for ; Tue, 22 Jun 1999 17:15:56 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by farabi.math.uh.edu (8.9.1/8.9.1) with ESMTP id QAB08759; Tue, 22 Jun 1999 16:15:20 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Tue, 22 Jun 1999 16:16:12 -0500 (CDT) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id QAA15706 for ; Tue, 22 Jun 1999 16:16:02 -0500 (CDT) Original-Received: from beaver.jprc.com (BEAVER.JPRC.COM [207.86.147.217]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id RAA13614 for ; Tue, 22 Jun 1999 17:15:02 -0400 (EDT) Original-Received: (from karl@localhost) by beaver.jprc.com (8.8.7/8.8.7) id RAA17915; Tue, 22 Jun 1999 17:14:32 -0400 Original-To: ding@gnus.org X-Face: "5(T0tZd{6}pd~YzBG8O/*EW,.]6]@`m^e;fv65W^Y&=d"M\1H}>T~4_.kcDD.O~y3k)a6h R;Nmi>9|>Nm${2IpM0^RcUEa\jcq?KOP)C&~x51l~zCHTulL^_T|u0I^kB'z@]{`2YjQu Original-Lines: 43 User-Agent: Gnus/5.070088 (Pterodactyl Gnus v0.88) XEmacs/21.2 (Chiyoda) Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:23462 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:23462 1. Send yourself a test message -- normal message, text/plain. 2. Forward that message to yourself -- an inline message/rfc822. 3. Forward *that* message to yourself. You now have an inline message/rfc822 containing another inline message/rfc822. p0.88's display of this will be...confused. Assuming that you prefix each forwarding with a bit of text/plain as well, you will see: [1. text/plain] containing the "outermost" (3rd level) new text. [2. message/rfc822] containing nothing but (in my case) an X-Sent: header (which BTW erroneously duplicates the topmost X-Sent; I sent a bug report about this last week). [3. text/plain] containing the 2nd level text which prefaced the original message on 1st forwarding... *followed by* the entire remaining message displayed as text/plain, including both the 2nd level and 1st level messages... all as part of a single "3." section. [4. message/rfc822] containing the original, 1st level forwarded message. Note that the innermost, original text is duplicated in both the 3. and 4. sections. Perhaps significantly, the buttonized (`K b') display of these sections will show the button areas as [1. text/plain] in *bold* [2. message/rfc822] in *bold* [3. text/plain] in /italic/ [4. message/rfc822] in *bold* Shouldn't these be labelled something hierarchical anyway, such as 1., 2., 2.1, 2.2, 2.2.1? Something Truly Evil happened to MIME interpretation recently... --karl