Gnus development mailing list
 help / color / mirror / Atom feed
* #<buffer  *nntpd*> and split-fancy-:-unparseable base64-encoded header.
@ 2018-09-22 20:23 Garreau, Alexandre
  2018-09-22 21:01 ` Adam Sjøgren
  0 siblings, 1 reply; 2+ messages in thread
From: Garreau, Alexandre @ 2018-09-22 20:23 UTC (permalink / raw)
  To: ding

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 :/



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-09-22 21:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-09-22 20:23 #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header Garreau, Alexandre
2018-09-22 21:01 ` Adam Sjøgren

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).