public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Chuck Hallenbeck <chuckh@ftml.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Spam protection strategies, was:x ot, spamassassin question
Date: Thu, 21 Jan 2010 17:41:01 -0500	[thread overview]
Message-ID: <20100121224101.GB6079@rx.localhost> (raw)
In-Reply-To: <20100121195602.GA21121@romuald.net.eu.org>

Greg, John, and all

On Thu, Jan 21, 2010 at 12:56:02PM -0700, Gregory Nowak wrote:
> 
> yes, like I said before, I have my script run every 24 hours on the
> messages my mom left as misidentified spam, or ham, so sa-learn is
> being trained that way. Also, yes, the messages are being segregated
> based on the x-spam-status header using maildrop actually, since I
> personally prefer that to procmail. Thanks again.
> 
> Greg

Congratulations on taming your spamassassin configuration. I just
finished installing a different spam protection here, much easier, and
with a different strategy. It uses vipul's "razor" and integrates
nicely with procmailrc and mutt. Razor is a collaborative spam
protection scheme, and works a lot like "denyhosts" in that false
positives and false negatives are reported to a distributed set of
hosts one by one as they are encountered, and each email the user
checks for spam is tested against the collective data base. It is the
consensus of razor users that distinguishes between ham and spam, and
that consensus is constantly being updated as the FP's and FN's are
reported. Also, each user acquires a "trust level" as his reports are
made, based on the soundness of his judgment in making the report.

Advantages: It's a smart filter out of the box, already trained by
other users.

Disadvantages: It doesn't work too well if an individual user has
ideosyncratic criteria for distinguishing ham/spam, since it stresses
group consensus on that question.

I divert incoming mail that is flagged by razor to a spam folder, and
occasionally scan it for false positives, reporting them when I find
them, by a keypress in mutt. As I examine mail that has not been
flagged and diverted to my spam folder, I occasionally find a false
negative, and simply report that to the network by another mutt
keypress.

I wonder what your thoughts are about such a collaborative data base
for spam protection?  It seems to me that it has some strengths that
"going it alone" with the bayesian model for isolated individuals may
lack.


Chuck



-- 
The Moon is Waxing Crescent (35% of Full)
      Either of these web addresses will take you to my web site:
          www.mhcable.com/~chuckh, or www.hallenbeck.ftml.net
                Audio editor weblog: edway.wordpress.com
               Or jabber 1on1 with me, chuckh1@jabber.org
                                --------
 People in general do not willingly read if they have anything else to
amuse them. -- S. Johnson
 

  reply	other threads:[~ UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Gregory Nowak
 ` trev.saunders
 ` John G. Heim
   ` Sina Bahram
   ` Gregory Nowak
     ` John G. Heim
       ` Gregory Nowak
         ` John G. Heim
   ` Gregory Nowak
     ` John G. Heim
       ` Gregory Nowak
         ` Gregory Nowak
         ` John G. Heim
           ` Gregory Nowak
             ` Chuck Hallenbeck [this message]
               ` Spam protection strategies, was:x " John G. Heim

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=20100121224101.GB6079@rx.localhost \
    --to=chuckh@ftml.net \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).