From: vvv@vsu.ru
Subject: content-transfer-encoding
Date: 09 Jan 2001 13:37:37 +0300 [thread overview]
Message-ID: <eyr92dqadq.fsf@video.uic.vsu.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]
Hi,
rfc2045 has the following requirement:
RFC> It should also be noted that, by definition, if a composite entity
RFC> has a transfer-encoding value such as "7bit", but one of the enclosed
RFC> entities has a less restrictive value such as "8bit", then either the
RFC> outer "7bit" labelling is in error, because 8bit data are included,
RFC> or the inner "8bit" labelling placed an unnecessarily high demand on
RFC> the transport system because the actual included data were actually
RFC> 7bit-safe.
but when gnus sends a multipart messages, it does not set the
content-transfer-encoding=8bit of the whole message when one of the
parts has 8bit (or content-transfer-encoding=binary when one of the
parts has binary CTE).
by default, the CTE, if omitted, is assumed to be 7bit (as stated in
the same RFC).
This message has a part with 8bit CTE, but gnus does not set the 8bit
CTE for the whole message.
Best,
v.
[-- Attachment #2: Type: text/plain, Size: 37 bytes --]
this part has a 8bit CTE:
проба пера
next reply other threads:[~2001-01-09 10:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 10:37 vvv [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-01-13 10:23 Content-Transfer-Encoding Shigeki Uno
2000-01-13 11:14 ` Content-Transfer-Encoding Katsumi Yamaoka
2000-01-13 17:02 ` Content-Transfer-Encoding Shigeki Uno
2000-01-13 23:52 ` Content-Transfer-Encoding Katsumi Yamaoka
2000-01-14 18:18 ` Content-Transfer-Encoding Shigeki Uno
2000-04-21 13:22 ` Content-Transfer-Encoding Lars Magne Ingebrigtsen
2000-04-21 19:24 ` Content-Transfer-Encoding Pavel Janik ml.
2000-04-22 0:16 ` Content-Transfer-Encoding Lars Magne Ingebrigtsen
2000-04-22 8:43 ` Content-Transfer-Encoding Pavel Janik ml.
2000-04-22 12:28 ` Content-Transfer-Encoding Lars Magne Ingebrigtsen
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=eyr92dqadq.fsf@video.uic.vsu.ru \
--to=vvv@vsu.ru \
/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).