From: "Garreau\, Alexandre" <galex-713@galex-713.eu>
To: ding@gnus.org
Subject: #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header.
Date: Sat, 22 Sep 2018 22:23:10 +0200 [thread overview]
Message-ID: <j7g93wzzzzzz.z6s.xxuns.g6.gal@galex-713.eu> (raw)
I am unsure if this is an appropriate and well-descriptive subject for
this issue, please point it out to me otherwise.
I am currently splitting my mail with nnmail-split-fancy’s :, according
list-id content, and recently I noticed I got a lot of mail in garbage
directories named with long base64 strings: I then experimentally
noticed the buffer nnmail-split-fancy’s : acts on is still
base-64-encoded for utf-8 content. However some mailing-list of online
(but graded) course of my college must have something wrong because
since the description of its list-id is in utf-8, the list-id itself is
too!
List-Id: =?utf-8?B?IkZvcnVtIFDDqWRhZ29naXF1ZSIgPG1vb2RsZWZvcnVtMjUvbW9vZGxlQG0=?= =?utf-8?B?b29kbGV1Ym8udW5pdi1icmVzdC5mcj4=?=
And what I normally read is:
List-Id: "Forum Pédagogique" <moodleforum25/moodle@moodleubo.univ-brest.fr>
So the thing between angle-brackets is readable in normal message-mode
but not by :…
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 :/
next reply other threads:[~2018-09-22 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-22 20:23 Garreau, Alexandre [this message]
2018-09-22 21:01 ` Adam Sjøgren
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=j7g93wzzzzzz.z6s.xxuns.g6.gal@galex-713.eu \
--to=galex-713@galex-713.eu \
--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).