From: "Garreau\, Alexandre" <galex-713@galex-713.eu>
To: emacs-devel@gnu.org
Subject: #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header.
Date: Sun, 23 Sep 2018 02:04:44 +0200 [thread overview]
Message-ID: <cftn5zzzzzzz.t6m.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 :/
PS: I maybe posted this also on ding@gnus, I was unsure of which mailing-list
was was appropriated, now I think I realized I was unsubscribed from it
and there are no online archive I guess…
next reply other threads:[~2018-09-23 0:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 0:04 Garreau, Alexandre [this message]
2018-09-23 6:05 ` #<buffer *nntpd*> and split-fancy-:-unparseable base64-encoded header Teemu Likonen
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=cftn5zzzzzzz.t6m.xxuns.g6.gal@galex-713.eu \
--to=galex-713@galex-713.eu \
--cc=emacs-devel@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 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).