From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: posting-charset abolition
Date: Thu, 31 Oct 2002 09:30:07 -0500 [thread overview]
Message-ID: <4n3cqmy93k.fsf@benko.bwh.harvard.edu> (raw)
In-Reply-To: <yotlpttq940u.fsf@jpl.org> (Katsumi Yamaoka's message of "Thu, 31 Oct 2002 21:38:57 +0900")
On Thu, 31 Oct 2002, yamaoka@jpl.org wrote:
> You are right. Putting CTE:8 to 7-bit articles is absolutely
> harmless. However, it is closely reminded of vicious MUAs
> rampant all over the world. Possibly they became better than
> ancient times, though. (In old days, Japanese mails were in a
> wretched condition.) Although this is no more than a personal
> matter of taste, it is worthwhile to delete an excessive header,
> isn't it?
>
> rfc1521.txt:
> ..."Content-Transfer-Encoding: 7BIT" is assumed if the
> Content-Transfer-Encoding header field is not present.
>
> So, I want to do that if it is not a burden on Gnus.
I think the simplest programmatic solution is to scan the message
buffer right before sending, when it's already encoded, and add the
CTE: 8bit header if any 8-bit characters are detected. But I still
think this is unnecessary work for other than aesthetic reasons, as
very few MTAs today do 7bit CTE, and setting the header to 8bit is
harmless to 7bit data.
I don't understand the statement about "vicious MUAs rampant."
--
Ted Zlatanov
next prev parent reply other threads:[~2002-10-31 14:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 13:15 Katsumi Yamaoka
2002-10-31 9:12 ` Katsumi Yamaoka
2002-10-31 11:34 ` Ted Zlatanov
2002-10-31 12:38 ` Katsumi Yamaoka
2002-10-31 14:30 ` Ted Zlatanov [this message]
2002-11-01 2:43 ` Katsumi Yamaoka
2002-11-01 3:07 ` Ted Zlatanov
2002-11-01 6:51 ` Jesper Harder
2002-11-01 8:20 ` Katsumi Yamaoka
2002-11-01 12:33 ` Katsumi Yamaoka
2002-11-01 14:18 ` Jesper Harder
2002-11-01 15:54 ` Katsumi
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=4n3cqmy93k.fsf@benko.bwh.harvard.edu \
--to=tzz@lifelogs.com \
/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).