From: Katsumi Yamaoka <yamaoka@jpl.org>
To: info-gnus-english@gnu.org
Subject: Re: How can I split mails based on the header when it contains multi-byte words
Date: Thu, 05 Jul 2007 19:07:33 +0900 [thread overview]
Message-ID: <b4m644zyxi2.fsf@jpl.org> (raw)
In-Reply-To: <uir8zgs3y.fsf@mail.ustc.edu.cn>
>>>>> Xu Weijiang wrote:
> I have a problem when i am trying to use *nnmail-split-fancy*, which
> has no effect when the corresponding field contain multi-byte words.
> Finally I found that *nnmail-split-fancy* only matches with the
> original mail without decoding, and the subject is something like:
> Subject: =?gb2312?B?udjT2rG+0afG2tb60dDJ6sfr?=
> How can i config *nnmail-split-fancy* to do the match *after*
> decoding?
Set the variable `nnmail-mail-splitting-decodes' to t.
In addition, the value of the `nnmail-mail-splitting-charset'
variable is used for decoding non-MIME encoded string. The
value good for you may be `gb2312' or `undecided', I think.
next prev parent reply other threads:[~2007-07-05 10:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 8:41 Xu Weijiang
2007-07-05 10:07 ` Katsumi Yamaoka [this message]
2007-07-05 11:42 ` wiza
2007-07-06 4:06 ` Xu Weijiang
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=b4m644zyxi2.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=info-gnus-english@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.
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).