All of lore.kernel.org
 help / color / mirror / Atom feed
From: eazgwmir@umail.furryterror.org (Zygo Blaxell)
To: reiserfs-list@namesys.com
Subject: Re: Reiserfs, highquality meds source, low rates
Date: 19 Apr 2004 20:14:48 -0400	[thread overview]
Message-ID: <c61q1o$6bk$1@satsuki.furryterror.org> (raw)
In-Reply-To: 4083C0B0.6090607@mweb.co.za

In article <4083C0B0.6090607@mweb.co.za>, Cami  <camis@mweb.co.za> wrote:
>> i am just not sure how to kill THIS messages which look so....
>> they dont look like spam, even to me upon first look.
>
>If you were using SpamAssasin, you wouldn't get these..

I _am_ using SpamAssassin, and I got this.  

Actually, this has turned into a neat example of how to poison a Bayes filter.

The original spam got flagged on my system like this:

X-Spam-Status: No, hits=2.9 required=5.0 tests=BAYES_40,HTML_MESSAGE, 
	RCVD_IN_DYNABLOCK,RCVD_IN_RFCI,RCVD_IN_SORBS autolearn=no version=2.63

So this got through the usual SA rules, none of which give very high
scores, and even the Bayes filter isn't sure.

Then comes your message, with a quote of the original spam:

X-Spam-Status: No, hits=-3.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham  
	version=2.63

So...my Bayes filter just auto-trained itself on the contents of the
spam message...as ham.  If I now feed the original spam through SA
again, it gets BAYES_01, and a score of -1.5.  Clearly I'm going to be
receiving a _lot_ of these, at least until I batch them all up and feed
them to sa-learn to retrain the Bayes filter.

Folks, if you want to talk about spam on a (non-spam-related) mailing
list, please please please don't quote it, no matter how interesting it
may be.  Or at least, if you do quote it, be sure to include a sentence
or two that contains gratuitous references to the names of chemicals
often used to mitigate the effects of problems that may arise with men
and the organs they use to procreate.

-- 
Zygo Blaxell (Laptop) <zblaxell@feedme.hungrycats.org>
GPG = D13D 6651 F446 9787 600B AD1E CCF3 6F93 2823 44AD

  parent reply	other threads:[~2004-04-20  0:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-19  1:52 Reiserfs, highquality meds source, low rates Grosbeak E. Collating
2004-04-19 11:59 ` Alexander Lyamin
2004-04-19 12:06   ` Cami
2004-04-19 13:34     ` Alexander Lyamin
2004-04-19 13:41       ` Cami
2004-04-20  0:14     ` Zygo Blaxell [this message]
2004-04-20  4:55       ` Cami
2004-04-20 20:51         ` Alexander Lyamin
2004-04-19 12:39   ` Toby Dickenson
2004-04-19 13:40     ` Alexander Lyamin
2004-04-19 13:55       ` Hendrik Visage
2004-04-20  0:54       ` Michael James
2004-04-20 15:45         ` Hans Reiser
2004-04-20 20:02           ` Hubert Chan
2004-04-20 20:46             ` Alexander Lyamin
  -- strict thread matches above, loose matches on Subject: below --
2004-04-20 17:26 Burnes, James
2004-04-20 21:39 Burnes, James
2004-04-21 12:40 ` Alexander Lyamin
2004-04-21 12:53   ` Philippe Gramoullé

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='c61q1o$6bk$1@satsuki.furryterror.org' \
    --to=eazgwmir@umail.furryterror.org \
    --cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.