From: Teemu Likonen <tlikonen@iki.fi>
To: Alexandre Garreau <galex-713@galex-713.eu>
Cc: emacs-devel@gnu.org
Subject: Re: #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header.
Date: Sun, 23 Sep 2018 09:05:11 +0300 [thread overview]
Message-ID: <87bm8ohhpk.fsf@iki.fi> (raw)
In-Reply-To: <cftn5zzzzzzz.t6m.xxuns.g6.gal@galex-713.eu> (Alexandre Garreau's message of "Sun, 23 Sep 2018 02:04:44 +0200")
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
Alexandre Garreau [2018-09-23 02:04:44+02] wrote:
> How to make that readable? why doesn’t nnmail-split-fancy acts on a
> decoded buffer? I need this to correctly receive and track that mail
> :/
There is variable nnmail-mail-splitting-decodes which, with a non-nil
value, should cause the splitting mechanism to decode headers before
splitting.
--
/// Teemu Likonen - .-.. <https://keybase.io/tlikonen> //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-09-23 6:05 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 [this message]
2018-09-23 8:57 ` Garreau, Alexandre
2018-09-23 10:56 ` Teemu Likonen
2018-09-23 11:37 ` May t be the default for nnmail-mail-splitting-decodes in Emacs? (Was: Re: #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header) Garreau, Alexandre
2018-09-23 11:36 ` #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bm8ohhpk.fsf@iki.fi \
--to=tlikonen@iki.fi \
--cc=emacs-devel@gnu.org \
--cc=galex-713@galex-713.eu \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).