From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Content-Transfer-Encoding is quoted-printable but should be 8bit
Date: Tue, 27 May 2014 20:22:08 +0900 [thread overview]
Message-ID: <b4mioorjwkf.fsf@jpl.org> (raw)
In-Reply-To: <87d2ezcxpv.fsf@micropit.roche-blanche.homenet.org>
On Tue, 27 May 2014 12:39:08 +0200, Peter Münster wrote:
> When sending messages without mime-parts or with normal attachments, the
> Content-Transfer-Encoding is always 8bit. Examples:
[...]
> But when I sign a message, the Content-Transfer-Encoding becomes
> quoted-printable:
First of all, that is hard-coded in Gnus. But here is a recipe
to shoot yourself in the foot:
(defadvice mm-body-encoding (around dont-use-ultra-safe-encoding activate)
"Bind `mm-use-ultra-safe-encoding' to nil."
(let (mm-use-ultra-safe-encoding) ad-do-it))
I don't know what kind of an obstacle this causes, sorry.
next prev parent reply other threads:[~2014-05-27 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 10:39 Peter Münster
2014-05-27 11:22 ` Katsumi Yamaoka [this message]
2014-05-27 12:22 ` Peter Münster
2014-05-27 18:42 ` Russ Allbery
2014-05-27 20:38 ` Peter Münster
2014-05-28 15:51 ` Russ Allbery
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=b4mioorjwkf.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@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).