From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/30413 Path: main.gmane.org!not-for-mail From: Shenghuo ZHU Newsgroups: gmane.emacs.gnus.general Subject: Re: More on forwarding quoted-printable encoded messages Date: 26 Apr 2000 09:47:24 -0400 Organization: U of Rochester Sender: owner-ding@hpc.uh.edu Message-ID: <2nem7t0yab.fsf@tiger.jia.vnet> References: <87d7qc557e.fsf@psyche.evansnet> <2n8zy1l1ug.fsf@tiger.jia.vnet> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: main.gmane.org 1035166954 8349 80.91.224.250 (21 Oct 2002 02:22:34 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 02:22:34 +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 61987D051E for ; Wed, 26 Apr 2000 09:45:54 -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 IAB30614; Wed, 26 Apr 2000 08:45:53 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Wed, 26 Apr 2000 08:45:21 -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 IAA22238 for ; Wed, 26 Apr 2000 08:45:09 -0500 (CDT) Original-Received: from shenghuo.dhs.org (d181829df.rochester.rr.com [24.24.41.223]) by mailhost.sclp.com (Postfix) with ESMTP id 1314FD051E for ; Wed, 26 Apr 2000 09:45:28 -0400 (EDT) Original-Received: (from zsh@localhost) by shenghuo.dhs.org (8.10.0/8.10.0) id e3QDlOH26395; Wed, 26 Apr 2000 09:47:24 -0400 Original-To: ding@gnus.org X-Attribution: ZSH X-Face: 'IF:e51ib'Qbl^(}l^&4-J`'P!@[4~O|&k#:@Gld#b/]oMq&`&FVY._3+b`mzp~Jeve~/#/ ERD!OTe<86UhyN=l`mrPY)M7_}`Ktt\K+58Z!hu7>qU,i.N7TotU[FYE(f1;}`g2xj!u*l`^&=Q!g{ *q|ddto|nkt"$r,K$[)"|6,elPH= GJ6Q In-Reply-To: "=?iso-8859-1?q?Bj=F8rn?= Mork"'s message of "26 Apr 2000 14:39:27 +0200" Original-Lines: 40 User-Agent: Gnus/5.0805 (Gnus v5.8.5) Emacs/20.6 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:30413 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:30413 >>>>> "Bj=F8rn" =3D=3D Bj=F8rn Mork writes: Bj=F8rn> Steinar Bang writes: >> >>>>> Shenghuo ZHU : >>=20 >> > I don't think that the problem is simply the c-t-e of >> > message/rfc822. In the current version, the message/rfc822 part is >> > only charset-decoded (gnus-article-decode-hook). When the message = is >> > sent, the part is re-encoded. I don't think this is a right >> > solution. The message/rfc822 part should be unchanged or totally >> > decoded/re-encoded (mml <-> mime). The former solution is not >> > acceptable to many users, because those users may want to change t= he >> > content. In the latter solution, the c-t-e is not necessary at all. >>=20 >> According to RFC-2046 section 5.2.1 (covering message/rfc822), last >> paragraph, the only legal c-t-encodings for message/rfc822, are 7bit, >> 8bit, and binary. >>=20 >> The way I see it, this means that the only safe c-t-e to chose when >> creating a message/rfc822 part, would be 7bit, which according to >> RFC-2046 would require the message itself to be encoded before >> inclusion, and with any non-ASCII headers encododed according to >> RFC-2047 Bj=F8rn> I believe the forwarded message should be unchanged even if th= e it Bj=F8rn> violates RFC2046/7 e.g. by using 8bit headers. The message/rfc= 822 CTE=20 Bj=F8rn> would then be 8bit if the original message, including headers,= contains=20 Bj=F8rn> any 8bit chars, otherwise 7bit. RFC2046 does not require the f= orwarded=20 Bj=F8rn> message to comply with RFCs 2046-49. It even explicitly states= that the=20 Bj=F8rn> body of a message/rfc822 part does not need to be RFC822-confo= rmant! How Bj=F8rn> do you encode the forwarded message if it contains 8bit charac= ters but=20 Bj=F8rn> no CT/CTE headers? Isn't it better not to make any charset and= encoding=20 Bj=F8rn> choice for the final recipient, and therefore forward the mess= age=20 Bj=F8rn> untouched? I think it is better to let user choose whether to forward a message untouched or re-encoded. --=20 Shenghuo