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: Mon, 08 Feb 2016 02:27:16 +0100	[thread overview]
Message-ID: <87fux4vvnv.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.

I want to emphasize my total agreement with this to
anyone reading this still using the KILL system.

With minimal effort I've now setup the scoring system
to do exactly what some one hundred lines of creative
Elisp was (barely) able to do with the KILL system.

Ironically, it felt good writing all that Elisp, but
not as good as it feels now throwing it away :)

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



  parent reply	other threads:[~2016-02-08  1:27 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
     [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 [this message]
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=87fux4vvnv.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).