From: Bruce Stephens <bruce@cenderis.demon.co.uk>
Subject: Content-type-encoding of forwarded message/rfc822
Date: 17 Jun 1999 20:06:06 +0100 [thread overview]
Message-ID: <m3so7q3aw1.fsf@cenderis.demon.co.uk> (raw)
Why is the default for this 8bit?
Today, I forwarded (using S o m) an ordinary us-ascii message to an
internal mailing list, and it got stuck. It got stuck because it
turned into a MIME message with a body part that was message/rfc822,
with encoding 8bit. (It shouldn't have got stuck, of course---that's
a bug in our list expansion software.)
But anyway, why is a us-ascii message wrapped as 8bit? Doesn't Gnus
look, to guess the minimum encoding it can use?
next reply other threads:[~1999-06-17 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-17 19:06 Bruce Stephens [this message]
1999-07-03 10:29 ` 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=m3so7q3aw1.fsf@cenderis.demon.co.uk \
--to=bruce@cenderis.demon.co.uk \
/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).