From: Russ Allbery <rra@stanford.edu>
Subject: Re: nnml splitting on encoded headers
Date: Sat, 25 May 2002 17:00:19 -0700 [thread overview]
Message-ID: <yloff3aics.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <vaf7klsta10.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sat, 25 May 2002 19:25:15 +0200")
Kai =?iso-8859-15?q?Gro=DFjohann?= <Kai.Grossjohann@CS.Uni-Dortmund.DE> 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.
> Is this really true? Maybe fancy splitting matches on word
> boundaries only, but "=" is not part of a word, so it can never be
> start of a word. Maybe it works to add .* in front and rear of these
> regular expressions.
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.
Incidentally, though, Gnus *does* appear to decode first and then apply
score files. Is there any way around this so that one can use the same
patterns in score files for groups that are gatewayed mailing lists?
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2002-05-26 0:00 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 [this message]
2002-05-26 12:32 ` Mark Thomas
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=yloff3aics.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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).