From: Radu Butoi <rbutoi@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Sending mail: line wrapping and quoted-printable encoding
Date: Sat, 25 Apr 2020 20:24:42 -0400 [thread overview]
Message-ID: <prg88sijnlf9.fsf@butoi.nyc.corp.google.com> (raw)
In-Reply-To: <prg8eesbnloc.fsf@butoi.nyc.corp.google.com>
Radu Butoi <rbutoi@gmail.com> writes:
> Hello all,
>
> I've recently set up my mail in Emacs, and it works well. Gmail, though,
> doesn't support [1] format=flowed, resulting in the hard-to-read comb
> effect when viewing on mobile, which I'd like to avoid. Doing some more
> research, I see that the quoted-printable encoding (which Gmail does
> support [2], and I've confirmed) can also be used to avoid hard line
> breaks while keeping under the line length limit.
>
> Now, I'd like to configure Emacs to send mail using this encoding. To
> test this I overwrite `sendmail-program` to log what Emacs sends.
> Reading the message-mode and Emacs MIME manuals, I tried setting the
> following variables:
>
> (setq
> mm-content-transfer-encoding-defaults
> '((".*" quoted-printable))
> mm-body-charset-encoding-alist
> '((iso-8859-1 . quoted-printable)
> (utf-8 . quoted-printable))
> mm-use-ultra-safe-encoding t)
>
> When sending, no encoding to quoted-printable is done (and there's no
> Content-Transfer-Encoding header). To try to debug this further,
> inserted the following into a buffer and ran M-: (mml-to-mime)
>
> test test test <...longer than 78 columns...>
Sorry, I forgot to escape this. It should say (I was trying to write an
MML definition to explicitly set the encoding):
<#part type=3D3Dtext/plain encoding=3D3Dquoted-printable>
test test test <...longer than 78 columns...>
<#/part>
>
> And there is still no encoding header or wrapping with =. Does anyone
> know what is going on here?
>
> More generally, since I'm new to terminal-based email, what is the
> etiquette around hard-wrapping (or not)? Would it be rude to send
> paragraphs as one logical line (wrapped-in-transmission by
> quoted-printable) and expect people to soft-wrap?
>
> Thanks in advance,
> Radu
>
> [1]: https://useplaintext.email/, and many blog posts mentioning the
> same. It seems like Gmail used to support this, from the screenshot in
> https://github.com/legoscia/messages-are-flowing.
>
> [2]: https://mathiasbynens.be/notes/gmail-plain-text
next prev parent reply other threads:[~2020-04-26 0:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 0:19 Sending mail: line wrapping and quoted-printable encoding Radu Butoi
2020-04-26 0:24 ` Radu Butoi [this message]
2020-04-26 0:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-26 18:44 ` Radu Butoi
2020-04-27 7:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-04-26 8:00 ` Gregor Zattler
2020-04-26 18:44 ` Radu Butoi
2020-04-27 8:52 ` Gregor Zattler
2020-04-27 22:20 ` Radu Butoi
2020-04-28 14:37 ` Gregor Zattler
2020-05-05 21:44 ` Radu Butoi
2020-05-06 7:37 ` Gregor Zattler
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=prg88sijnlf9.fsf@butoi.nyc.corp.google.com \
--to=rbutoi@gmail.com \
--cc=help-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.