From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Matching split rules against decoded headers? (Was: Re: gnus-summary-respool-trace for nnimap?)
Date: Wed, 21 Nov 2001 17:33:07 +0100 [thread overview]
Message-ID: <vafhero6q4c.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <uoflwi09g.fsf_-_@axis.com> (Niklas Morberg's message of "Wed, 21 Nov 2001 16:58:35 +0100")
Niklas Morberg <niklas.morberg@axis.com> writes:
> Would it be a viable option to have split rules do the
> matching on decoded headers (still avoiding to decode the
> message body)?
Maybe. But don't count on it happening :-)
kai
--
Simplification good! Oversimplification bad! (Larry Wall)
next prev parent reply other threads:[~2001-11-21 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 10:49 gnus-summary-respool-trace for nnimap? Niklas Morberg
2001-11-21 12:40 ` Kai Großjohann
2001-11-21 13:33 ` Niklas Morberg
2001-11-21 15:31 ` Kai Großjohann
2001-11-21 15:58 ` Matching split rules against decoded headers? (Was: Re: gnus-summary-respool-trace for nnimap?) Niklas Morberg
2001-11-21 16:33 ` Kai Großjohann [this message]
2001-11-21 18:43 ` gnus-summary-respool-trace for nnimap? Paul Jarc
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=vafhero6q4c.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).