From: Jason Parker-Burlingham <jasonp@uq.net.au>
Subject: Re: kill file rule matching
Date: Thu, 29 May 2003 17:00:15 -0400 [thread overview]
Message-ID: <871xyhsc2o.fsf@freezer.burling> (raw)
In-Reply-To: <8765nt3f96.fsf@kruhft.vc.shawcable.net>
Burton Samograd <kruhft@hotmail.com> writes:
> I recently starting adding entries to my KILL file and I'm noticing
> that certain messages which shouldn't be killed are. I only have a
> couple of rules and they just match spam subjects so I'm a bit
> confused about how they are getting in there. In slrn there was a
> command to show the kill file rule that matches the current article.
> Is there any such function in gnus?
You can press `V t' in the summary buffer to get a score trace of the
article under the point.
I use this whenever I don't understand why an article is scored up or
down.
--
``Oooh! A gingerbread house! Hansel and Gretel are set for life!''
next parent reply other threads:[~2003-05-29 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8765nt3f96.fsf@kruhft.vc.shawcable.net>
2003-05-29 21:00 ` Jason Parker-Burlingham [this message]
[not found] ` <yoijof1l9que.fsf@helm.dd.chalmers.se>
[not found] ` <874r3d18ac.fsf@kruhft.vc.shawcable.net>
2003-05-30 4:55 ` 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=871xyhsc2o.fsf@freezer.burling \
--to=jasonp@uq.net.au \
/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).