Gnus development mailing list
 help / color / mirror / Atom feed
From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: More on forwarding quoted-printable encoded messages
Date: 26 Apr 2000 09:47:24 -0400	[thread overview]
Message-ID: <2nem7t0yab.fsf@tiger.jia.vnet> (raw)
In-Reply-To: "=?iso-8859-1?q?Bj=F8rn?= Mork"'s message of "26 Apr 2000 14:39:27 +0200"

>>>>> "Bjørn" == Bjørn Mork <bmork@dod.no> writes:

Bjørn> Steinar Bang <sb@metis.no> writes:
>> >>>>> Shenghuo ZHU <zsh@cs.rochester.edu>:
>> 
>> > 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 the
>> > content. In the latter solution, the c-t-e is not necessary at all.
>> 
>> 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.
>> 
>> 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ørn> I believe the forwarded message should be unchanged even if the it
Bjørn> violates RFC2046/7 e.g. by using 8bit headers. The message/rfc822 CTE 
Bjørn> would then be 8bit if the original message, including headers, contains 
Bjørn> any 8bit chars, otherwise 7bit. RFC2046 does not require the forwarded 
Bjørn> message to comply with RFCs 2046-49. It even explicitly states that the 
Bjørn> body of a message/rfc822 part does not need to be RFC822-conformant! How
Bjørn> do you encode the forwarded message if it contains 8bit characters but 
Bjørn> no CT/CTE headers? Isn't it better not to make any charset and encoding 
Bjørn> choice for the final recipient, and therefore forward the message 
Bjørn> untouched?

I think it is better to let user choose whether to forward a message
untouched or re-encoded.

-- 
Shenghuo



  parent reply	other threads:[~2000-04-26 13:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-05 10:11 Carey Evans
2000-04-20 23:25 ` Lars Magne Ingebrigtsen
2000-04-21 13:59   ` Steinar Bang
2000-04-21 18:42     ` Lars Magne Ingebrigtsen
2000-04-21 20:46       ` Steinar Bang
2000-04-22 12:04         ` Lars Magne Ingebrigtsen
2000-04-23 10:58           ` Steinar Bang
2000-04-23 19:08             ` Lars Magne Ingebrigtsen
2000-04-23 19:50               ` Steinar Bang
2000-04-24 14:29                 ` Lars Magne Ingebrigtsen
2000-04-24 18:03                   ` Steinar Bang
2000-04-26  6:23                     ` Steinar Bang
2000-04-26  8:10                       ` Shenghuo ZHU
2000-04-26  8:23                         ` Steinar Bang
2000-04-26 12:39                           ` Bjørn Mork
2000-04-26 13:14                             ` Steinar Bang
2000-04-26 13:47                             ` Shenghuo ZHU [this message]
2000-04-26 13:52                               ` Roman Belenov
2000-04-26 14:23                                 ` Shenghuo ZHU
2000-04-26 13:57                               ` Steinar Bang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2nem7t0yab.fsf@tiger.jia.vnet \
    --to=zsh@cs.rochester.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).