From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: sometime splits
Date: Fri, 02 Nov 2012 18:00:42 +0900 [thread overview]
Message-ID: <b4mobjg5qh1.fsf@jpl.org> (raw)
In-Reply-To: <87wqy4qw8v.fsf@ericabrahamsen.net>
Eric Abrahamsen wrote:
> Subject: =?utf-8?q?=5BPaper_Republic=5D_New_Comment_on_French_Rendition_of_Fan_Wen?=
> =?utf-8?b?4oCZcyDigJxIYXJtb25pb3VzIExhbmTigJ0gdG8gTGF1bmNoIGJ5IGVhcmx5?=
> =?utf-8?q?_2013_MARKED_SPAM?=
> Not surprisingly, the call to (rx "MARKED SPAM" eol) fails on this,
> because of the extra "?=" at the end of the header, and the underscore
> between MARKED and SPAM.
How about setting `nnmail-mail-splitting-decodes' to t?
This makes Gnus decode encoded headers before splitting, though
it might make splitting slow a bit.
next prev parent reply other threads:[~2012-11-02 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 18:41 Eric Abrahamsen
2012-03-27 20:16 ` Russ Allbery
2012-03-27 21:29 ` Eric Abrahamsen
2012-11-02 7:50 ` Eric Abrahamsen
2012-11-02 9:00 ` Katsumi Yamaoka [this message]
2012-11-02 9:39 ` 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=b4mobjg5qh1.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).