From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: bugs@gnus.org
Subject: Re: elisp encoding
Date: Thu, 01 Jul 2004 18:15:34 +0900 [thread overview]
Message-ID: <b9y6598f5qh.fsf@jpl.org> (raw)
In-Reply-To: <868ye5z6fp.fsf@rumba.de.uu.net>
>>>>> In <868ye5z6fp.fsf@rumba.de.uu.net>
>>>>> Kai Grossjohann <kai@emptydomain.de> wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> I don't know why the part was modified into quoted-printable
>> from 8bit, but it may be doing of MTAs.
> I think it makes sense to use qp encoding for long lines, by breaking
> them with the "= at end of line" trick.
> That would explain why CTE qp might be useful. Perhaps someone
> overlooked this when they changed from qp to 8bit?
Thanks. Now I'm sure the 8bit-to-qp conversion has been done by
a certain MTA. It is useful when a message contains very long
lines of over 998 bytes. ShengHuo may have entrusted folding of
them to MTA. However, every MTA always doesn't do so.
>>>>> In <027c40e2d84907-gin@mo.msk.ru>
>>>>> "Ilya N. Golubev" <gin@mo.msk.ru> wrote:
[...]
> This certainly is not the processing of long lines in body parts as
> specified by RFC 2045, which imposes line length limit of 998 octets,
> and which concerns both 7bit and 8bit transfer encodings.
So, I think Gnus should fold very long lines by itself. An easy
way to do that is to replace all `8bit's with `quoted-printable'
in the mm-content-transfer-encoding-defaults variable. WDYT?
(let (e)
(while (setq e (rassoc '(8bit)
mm-content-transfer-encoding-defaults))
(setcdr e '(quoted-printable))))
Even if it is done, 7bit is used for short ascii lines.
> Another bug of current processing is that it may leave an 8bit body
> part with lines longer than allowed by RFC 2045. Actually observed
> such a standard violation.
> . Created an `.el' file containing 1 pure 7bit line of 1500 octets.
> . Attached it to message.
> . Evaluated `(mml-to-mime)'.
I also tested it sending the .newsrc.eld file to me. The
contents were completely broken by MTA.
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2004-07-01 9:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ufu0wuicqb.fsf@d-fens.mopniei.ru>
2004-06-30 5:50 ` Katsumi Yamaoka
2004-06-30 6:09 ` Katsumi Yamaoka
2004-06-30 8:24 ` Katsumi Yamaoka
2004-06-30 15:12 ` Ilya N. Golubev
[not found] ` <cbttc8$eop$2@quimby.gnus.org>
2004-06-30 10:27 ` Kai Grossjohann
2004-07-01 9:15 ` Katsumi Yamaoka [this message]
2004-07-01 9:30 ` Katsumi Yamaoka
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=b9y6598f5qh.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=bugs@gnus.org \
/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).