From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/30105 Path: main.gmane.org!not-for-mail From: Steinar Bang Newsgroups: gmane.emacs.gnus.general Subject: Re: More on forwarding quoted-printable encoded messages Date: 21 Apr 2000 22:46:26 +0200 Sender: owner-ding@hpc.uh.edu Message-ID: References: <87d7qc557e.fsf@psyche.evansnet> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035166678 6689 80.91.224.250 (21 Oct 2002 02:17:58 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 02:17:58 +0000 (UTC) Return-Path: Original-Received: from lisa.math.uh.edu (lisa.math.uh.edu [129.7.128.49]) by mailhost.sclp.com (Postfix) with ESMTP id 7324CD051E for ; Fri, 21 Apr 2000 16:46:57 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by lisa.math.uh.edu (8.9.1/8.9.1) with ESMTP id PAB27583; Fri, 21 Apr 2000 15:46:56 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Fri, 21 Apr 2000 15:46:25 -0500 (CDT) Original-Received: from mailhost.sclp.com (postfix@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id PAA07306 for ; Fri, 21 Apr 2000 15:46:16 -0500 (CDT) Original-Received: from viffer.metis.no (gran.metis.no [193.90.64.36]) by mailhost.sclp.com (Postfix) with ESMTP id D80DAD051E for ; Fri, 21 Apr 2000 16:46:30 -0400 (EDT) Original-Received: (from sb@localhost) by viffer.metis.no (8.9.3/8.9.3) id WAA15376; Fri, 21 Apr 2000 22:46:26 +0200 Original-To: ding@gnus.org In-Reply-To: Lars Magne Ingebrigtsen's message of "21 Apr 2000 20:42:57 +0200" Original-Lines: 24 User-Agent: Gnus/5.0804 (Gnus v5.8.4) XEmacs/20.4 (Emerald) Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:30105 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:30105 >>>>> Lars Magne Ingebrigtsen : > Steinar Bang writes: >> Yes. But Gnus does it wrong when it q-ps the message/rfc822 part, I >> think (I sent a bug report for this). Shouldn't the message itself be >> q-p if neccessary? > Yes. But what if you're forwarding something with 8bit headers? > (I remember the RFCs saying this is a no-no, but, er.) According to the relevant quote from the MIME standards (the one in my bug report is inconclusive) http://www.ietf.org/rfc/rfc2046.txt section 5.2.1 (covering message/rfc822), last paragraph: No encoding other than "7bit", "8bit", or "binary" is permitted for the body of a "message/rfc822" entity. The message header fields are always US-ASCII in any case, and data within the body can still be encoded, in which case the Content-Transfer-Encoding header field in the encapsulated message will reflect this. Non-US-ASCII text in the headers of an encapsulated message can be specified using the mechanisms described in RFC 2047. it would seem that the headers should be RFC2047-ified if neccessary.