From: Sven Luther <sven.luther@wanadoo.fr>
To: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
Cc: caml <caml-list@inria.fr>
Subject: Re: [Caml-list] Who controls INRIA mailserv filters?
Date: Thu, 12 Aug 2004 09:50:15 +0200 [thread overview]
Message-ID: <20040812075015.GA15804@pegasos> (raw)
In-Reply-To: <OOEALCJCKEBJBIJHCNJDCEFDHGAB.vanevery@indiegamedesign.com>
On Thu, Aug 12, 2004 at 12:36:02AM -0700, Brandon J. Van Every wrote:
> don groves wrote:
> > At 14:22 8/11/2004, don groves wrote:
> > >At 13:29 8/11/2004, Brandon J. Van Every wrote:
> > >
> > >Maybe if you spelled S*attle correctly the filter would pass it.
> > >Most, if not all, words with embedded non-alpha characters these
> > >days are ads for V!agr@ or C!@lis so the filter gets trained
> > on those.
> >
> > Nope, that's not it ;)
>
> I am unsure of your antecedant, so I'm unsure what you mean by your
> followup.
>
> If you look at the X-Sp*m header of your 2 posts, you will see a list of
> words. Those with high values like 99's increase the likelihood that
> your post will be classified as sp*m. That is why I use an asterisk
> with them. The problem words in your own posts are:
>
> brand*n
> spell*d
> s*attle
> agggggr (only 1 g, probably part of vairga (letters transposed to
> protect us all))
> addddds (only 1 d)
> traff*c
>
> Bear in mind that each and every one of my posts carries an automatic
> strike against me. Even though I'm willing to use Brand*n in my
> signature, I'm totally unwilling to create a separate e-mail identity
> just for caml-list. So every one of my posts has 1 correctly spelled
> occurrance of Brand*n in it.
>
> I bet, furthermore, that you will not see the word S*attle (correctly
> spelled) in the X-sp*m header of this post. This would disprove your
> claim about * being a red flag for the filter, unless the filter does
> not in fact report full information about how it makes its decisions.
Bah, just do as spammers do, and quote a considerable portion of one of
Xavier's posts to this list as a signature. Works like a charm for spammers to
defeat bayesian filters, so should be ok for you too.
Friendly,
Sven Luther
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-08-12 7:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-11 4:45 Brandon J. Van Every
2004-08-11 6:53 ` Diego Olivier Fernandez Pons
2004-08-11 20:29 ` Brandon J. Van Every
2004-08-11 21:22 ` don groves
2004-08-11 21:26 ` don groves
2004-08-12 7:36 ` Brandon J. Van Every
2004-08-12 7:50 ` Sven Luther [this message]
2004-08-12 8:28 ` Diego Olivier Fernandez Pons
2004-08-12 9:22 ` Brandon J. Van Every
2004-08-12 9:28 ` Xavier Leroy
2004-08-12 12:59 ` [Caml-list] OCaml growing pains Brandon J. Van Every
2004-08-12 14:58 ` Mikhail Fedotov
2004-08-12 21:30 ` Brandon J. Van Every
2004-08-13 6:05 ` skaller
2004-08-13 7:07 ` Brandon J. Van Every
2004-08-13 8:52 ` Mikhail Fedotov
[not found] <OOEALCJCKEBJBIJHCNJDAEFIHGAB.vanevery@indiegamedesign.com>
2004-08-12 12:09 ` [Caml-list] Who controls INRIA mailserv filters? Brandon J. Van Every
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=20040812075015.GA15804@pegasos \
--to=sven.luther@wanadoo.fr \
--cc=caml-list@inria.fr \
--cc=vanevery@indiegamedesign.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