Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: spam*.el and ifile-gnus.el?
Date: Sun, 29 Dec 2002 14:06:09 -0500	[thread overview]
Message-ID: <m3y968y7a6.fsf@heechee.beld.net> (raw)
In-Reply-To: <m3vg1czpqv.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 29 Dec 2002 18:42:00 +0100")

On Sun, 29 Dec 2002, larsi@gnus.org wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
> 
>> This is (to quote the comment) a bit raw, but the idea is that
>> whatever is marked as spam when you exit a spam group should be
>> reported as spam.  Reporting may mean bogofilter processing, ifile
>> submission, or submission to a spam service.
> 
> But the submission thing hasn't been written yet, I guess?

Not AFAIK.  I would allow the user to pipe it through an external
submitter, because the spam reporting logic is very complex if done
right.

Of course, these days reporting spam is becoming less useful since
spammers have started forging the message headers that let users trace
the message to the origin.

>> Ideas and patches to spam.el are welcome, of course.
> 
> I want to use spam.el now, but I'm not quite sure what's the
> recommended thing to use.  I think I want to let my mail be split as
> I normally do now, but have the non-classified mail be passed to
> something that will say whether it's spam or not.  Which is provided
> nicely by spam.el, but I wonder whether bogofilter or ifile is
> bestest?

That decision is up to you - spam.el is just intended to be a way for
users to choose their preferred way of sorting spam from non-spam.

Bogofilter is decent, and Kai and others swear by ifile.

<editorial>

I don't like statistical spam filters, personally, because they are
easily fooled.  Legitimate messages can look like spam (for instance,
a report of spam that crashes Gnus); spammers can easily insert
legitimate text in the message to offset word and sentence statistics.

I know statistical analysis is fashionable now, but there's no way
short of designing a full AI that spam can be identified by content
analysis.  We call a message spam when it's unsolicited, commercial,
and annoying.  Content can only determine the commercial nature of a
message, and even that is somewhat doubtful.  There's lots of messages
that meet only 2 of those three criteria.  I wouldn't want to classify
those messages as spam.

</editorial>

I think ORDB and such are the best way to detect spam.  Unfortunately
blackholes don't work in spam.el because of a bug in the DNS code I
reported a while ago; you may want to take a look at that.  I don't
think it was ever fixed, but Simon Josefsson may have looked at it.

> (And gnus-ifile.el isn't in the Gnus distribution.  It probably
> should be, right?)

That's up to the gnus-ifile.el author, I think he wanted to wait until
the package works with more backends.  I'm coming out of a long
Christmas break, sorry if I'm forgetting something...  My brain is not
up to non-holiday speed yet :)

Ted




  reply	other threads:[~2002-12-29 19:06 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
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 [this message]
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=m3y968y7a6.fsf@heechee.beld.net \
    --to=tzz@lifelogs.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).