Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: auto-kill mails with "X-Spam-Flag: YES"
Date: Sun, 07 Feb 2016 05:39:00 +0100	[thread overview]
Message-ID: <87mvrdkucb.fsf@debian.uxu> (raw)
In-Reply-To: <87lh6xfabl.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

> I would also recommend using scoring instead
> of killing.

OK, I did this:

    (setq gnus-extra-headers '(To Cc Keywords Gcc Newsgroups X-Spam-Flag))

And in ~/News/nnml:mail.misc.SCORE

    (("extra"
      ("YES" -1000 nil e "X-Spam-Flag")))

But still with `V t' it says

    No score rules apply to the current article (default score 0).

even tho that file has

    X-Spam-Flag: YES

Do I have to enable scoring explicitly?

-- 
underground experts united
http://user.it.uu.se/~embe8573



  reply	other threads:[~2016-02-07  4:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3558.1454557630.843.info-gnus-english@gnu.org>
2016-02-07  3:50 ` Lars Ingebrigtsen
2016-02-07  4:39   ` Emanuel Berg [this message]
     [not found]   ` <mailman.3850.1454819959.843.info-gnus-english@gnu.org>
2016-02-07  4:44     ` Lars Ingebrigtsen
2016-02-07  5:01       ` Emanuel Berg
     [not found]       ` <mailman.3852.1454821323.843.info-gnus-english@gnu.org>
2016-02-07  5:23         ` Lars Ingebrigtsen
2016-02-08  0:48           ` Emanuel Berg
     [not found]           ` <mailman.3977.1454892539.843.info-gnus-english@gnu.org>
2016-02-08  4:48             ` Lars Ingebrigtsen
2016-02-08 22:52               ` Emanuel Berg
     [not found]               ` <mailman.4132.1454971965.843.info-gnus-english@gnu.org>
2016-02-08 23:39                 ` Lars Ingebrigtsen
2016-02-09  2:26                   ` Emanuel Berg
     [not found]                   ` <mailman.4158.1454984781.843.info-gnus-english@gnu.org>
2016-02-09 23:47                     ` Lars Ingebrigtsen
2016-02-10  0:50                       ` Emanuel Berg
     [not found]                       ` <mailman.4270.1455065439.843.info-gnus-english@gnu.org>
2016-02-10  3:04                         ` Lars Ingebrigtsen
2016-02-11  0:50                           ` Emanuel Berg
     [not found]                           ` <mailman.4358.1455151881.843.info-gnus-english@gnu.org>
2016-02-11  4:01                             ` Lars Ingebrigtsen
2016-02-17  0:38                               ` Emanuel Berg
     [not found]                               ` <mailman.4888.1455669521.843.info-gnus-english@gnu.org>
2016-02-20  8:34                                 ` Lars Ingebrigtsen
2016-02-21  0:44                                   ` Emanuel Berg
     [not found]                                   ` <mailman.5253.1456015518.843.info-gnus-english@gnu.org>
2016-02-21  2:43                                     ` Lars Ingebrigtsen
2016-02-21  3:29                                       ` Emanuel Berg
2016-02-08  1:27   ` Emanuel Berg
2016-02-04  3:46 Emanuel Berg

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=87mvrdkucb.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --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).