From: Mark Thomas <swoon@bellatlantic.net>
Subject: Re: nnml splitting on encoded headers
Date: Sun, 26 May 2002 08:32:10 -0400 [thread overview]
Message-ID: <wf1u1ovf9fp.fsf@svelte.home> (raw)
In-Reply-To: <yloff3aics.fsf@windlord.stanford.edu>
Russ Allbery <rra@stanford.edu> writes:
>> Mark Thomas <swoon@bellatlantic.net> writes:
>
>>> I have split rules:
>>> ("subject" "=\\?euc-kr\\?" "mail.spam.asian")
>>> ("subject" "=\\?ks_c_5601-1987\\?" "mail.spam.asian")
>>> but these don't to work because Gnus has already decoded the
>>> messages.
> Kai's right. It does work; I use this all the time. It isn't Gnus
> decoding that's stopping this from working, but is instead the fact
> that Gnus by default expects word boundaries on either side of the
> pattern so you have to add .* before and after.
Yes, these will never match because of the word boundary rule. (I
don't normally use fancy splitting because I don't like that
restriction. Unfortunately, gnus-summary-respool-trace doesn't tell
you which regexp matched if you don't use fancy splitting. In trying
to figure out what was happening, I quickly translated my normal split
rules to fancy rules and I had missed this.)
However, Gnus decodes the headers before running the split rules.
Check out this ChangeLog entry:
2002-01-26 Lars Magne Ingebrigtsen <larsi@gnus.org>
* nnmail.el (nnmail-article-group): Decode headers before running
split rules over them.
(nnmail-mail-splitting-charset): New variable.
and this snippet of code from nnmail-article-group:
;; Decode MIME headers and charsets.
(let ((mail-parse-charset nnmail-mail-splitting-charset))
(mail-decode-encoded-word-region (point-min) (point-max)))
Cheers,
-Mark
next prev parent reply other threads:[~2002-05-26 12:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 20:10 Mark Thomas
2002-05-25 12:35 ` Mark Thomas
2002-05-25 17:25 ` Kai Großjohann
2002-05-26 0:00 ` Russ Allbery
2002-05-26 12:32 ` Mark Thomas [this message]
2002-05-30 22:21 ` Russ Allbery
2002-06-03 3:34 ` Jesper Harder
2002-06-03 17:52 ` Simon Josefsson
2002-06-03 19:41 ` Kai Großjohann
2002-06-03 19:48 ` Simon Josefsson
2002-06-03 20:04 ` Russ Allbery
2002-05-28 20:45 ` Norman Walsh
2002-05-28 22:17 ` Mark Thomas
2002-05-29 0:31 ` Russ Allbery
2002-05-29 7:39 ` Kai Großjohann
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=wf1u1ovf9fp.fsf@svelte.home \
--to=swoon@bellatlantic.net \
/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).