Gnus development mailing list
 help / color / mirror / Atom feed
From: Clemens Fischer <ino@despammed.com>
Subject: Re: spam*.el and ifile-gnus.el?
Date: Mon, 30 Sep 2002 23:40:11 +0200	[thread overview]
Message-ID: <vg4nupfo.fsf@ID-23066.news.dfncis.de> (raw)
In-Reply-To: <m3bs6fpdv9.fsf@heechee.beld.net>

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Fri, 13 Sep 2002, kohrs@castify.net wrote:
>> Second, would ifile make sense on headers only, for spam decisions ?
>
> I think so, I am able to visually distinguish spam messages in about
> 95% of the cases based on the subject: header alone, in the summary
> buffer.  Spam messages are generally about things you don't care about :)

letting ifile judge on the subject line alone if it usually gets
messages in toto may give wrong results.  or maybe if it is really
only the subject line, then you'll miss "only" the porn spams saying
"hello, darling" or "back from vacation".  chances rise if you feed
all of the headers, but full accuracy comes from full data, as always.

clemens





  reply	other threads:[~2002-09-30 21:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-10 17:36 Kai Großjohann
2002-09-10 20:56 ` Alex Schroeder
2002-09-11  9:59   ` Kai Großjohann
2002-09-12  0:05     ` David Aspinwall
2002-09-12 15:35       ` Arnd Kohrs
2002-09-13  4:21         ` Jeremy H. Brown
2002-09-13  6:37           ` Andreas Fuchs
2002-09-13  7:17             ` Jeremy H. Brown
2002-09-13  7:50               ` Arnd Kohrs
2002-09-14  7:39                 ` Simon Josefsson
2002-09-15 18:16                 ` Jeremy H. Brown
2002-09-30 17:48                 ` Ted Zlatanov
2002-09-30 21:40                   ` Clemens Fischer [this message]
2002-09-13 11:20           ` Kai Großjohann
2002-09-15 18:16             ` Jeremy H. Brown
2002-09-13  3:39       ` Jeremy H. Brown
2002-09-30 17:54 ` Ted Zlatanov
2002-12-29 17:42   ` Lars Magne Ingebrigtsen
2002-12-29 19:06     ` Ted Zlatanov
2002-12-29 19:29       ` Lars Magne Ingebrigtsen

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=vg4nupfo.fsf@ID-23066.news.dfncis.de \
    --to=ino@despammed.com \
    /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).