From: "Garreau\, Alexandre" <galex-713@galex-713.eu>
To: Teemu Likonen <tlikonen@iki.fi>, emacs-devel@gnu.org
Subject: May t be the default for nnmail-mail-splitting-decodes in Emacs? (Was: Re: #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header)
Date: Sun, 23 Sep 2018 13:37:25 +0200 [thread overview]
Message-ID: <lnk7gtzzzzzz.qhz.xxuns.g6.gal_-_@galex-713.eu> (raw)
In-Reply-To: <87in2w32is.fsf@iki.fi> (Teemu Likonen's message of "Sun, 23 Sep 2018 13:56:59 +0300")
On 2018-09-23 at 13:56, Teemu Likonen wrote:
> Alexandre Garreau [2018-09-23 10:57:57+02] wrote:
>> Why isn’t this behavior the default? is there any advantage to parse
>> the yet-encoded content (maybe its encoding?) or still big issue by
>> decoding before rather than after?
>
> I don't know but I certainly think that non-nil would be better default
> for nnmail-mail-splitting-decodes. Encoded headers are the norm (MIME)
> and only decoded headers are meaningful for people and mail splitting.
> The receiver can't control whether the headers come in encoded or plain
> format.
May it be t by default in next release then? have any maintainer saw
this to give their mind?
It’d be fantastic to see once more my config shrinking because of better
defaults!
next prev parent reply other threads:[~2018-09-23 11:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 0:04 #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header Garreau, Alexandre
2018-09-23 6:05 ` Teemu Likonen
2018-09-23 8:57 ` Garreau, Alexandre
2018-09-23 10:56 ` Teemu Likonen
2018-09-23 11:37 ` Garreau, Alexandre [this message]
2018-09-23 11:36 ` Andreas Schwab
2018-09-23 11:43 ` Garreau, Alexandre
2018-09-23 11:50 ` Andreas Schwab
2018-09-23 12:30 ` Why nnmail-mail-splitting-decodes defaults to nil (Was: Re: #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header) Garreau, Alexandre
2018-09-27 22:05 ` Why nnmail-mail-splitting-decodes defaults to nil Eric Abrahamsen
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=lnk7gtzzzzzz.qhz.xxuns.g6.gal_-_@galex-713.eu \
--to=galex-713@galex-713.eu \
--cc=emacs-devel@gnu.org \
--cc=tlikonen@iki.fi \
/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.