From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /mail/lib/patterns
Date: Wed, 26 Mar 2003 11:23:39 +0100 [thread overview]
Message-ID: <200303261023.h2QANdf03407@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Wed, 26 Mar 2003 09:42:27 +0000." <vi4k7enjio8.fsf@blue.cs.yorku.ca>
The funny thing is that, probably because you included the spam
assasin report, your message got classified as spam here.
here is the (slightly reformatted) report for your own message.
Axel.
SPAM: -------------------- Start SpamAssassin results ----------------------
SPAM: This mail is probably spam. The original message has been altered
SPAM: so you can recognise or block similar unwanted mail in future.
SPAM: See http://spamassassin.org/tag/ for more details.
SPAM:
SPAM: Content analysis details: (5.8 hits, 5 required)
SPAM: PORN_10 (0.6 points) BODY: Uses words and phrases which
indicate porn (10)
SPAM: AS_SEEN_ON (2.2 points) BODY: As seen on national TV!
SPAM: CLICK_BELOW (1.5 points) BODY: Asks you to click below
SPAM: DOUBLE_CAPSWORD (1.1 points) BODY: A word in all caps repeated
on the line
SPAM: GAPPY_TEXT (0.4 points) BODY: Contains 'G.a.p.p.y-T.e.x.t'
SPAM:
SPAM: -------------------- End of SpamAssassin results ---------------------
> it is also great fun to read its content analysis. here is one from
> last night (lightly reformatted)
next prev parent reply other threads:[~2003-03-26 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 19:10 Steve Simon
2003-03-17 19:32 ` Russ Cox
2003-03-17 19:56 ` Mark Powers
2003-03-26 9:42 ` ozan s yigit
2003-03-26 10:23 ` Axel Belinfante [this message]
2003-03-26 14:40 ` ozan s yigit
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=200303261023.h2QANdf03407@zamenhof.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--cc=9fans@cse.psu.edu \
/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).