From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] spam filtering fs
Date: Mon, 1 Sep 2003 16:49:33 +0200 [thread overview]
Message-ID: <037601c37098$424eb460$b9844051@insultant.net> (raw)
In-Reply-To: <04748aeba9f1d96bbf44451f8c131ef2@plan9.escet.urjc.es>
> You could assume that all mails that have not classified as spam, are not
> spam. I could then simply define a `S' script and run it from acme to
> let you know which ones are spam.
i used to do something like that on lunix:
http://www.insultant.net/repo/dws.html
i _cannot_ use acme. it's just not for me.
next prev parent reply other threads:[~2003-09-01 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <758707399@snellwilcox.com>
2003-09-01 14:36 ` steve.simon
2003-09-01 14:41 ` Fco.J.Ballesteros
2003-09-01 14:49 ` boyd, rounin [this message]
2003-09-01 12:48 steve.simon
2003-09-01 14:16 ` Fco.J.Ballesteros
2003-09-01 14:19 ` David Presotto
2003-09-01 14:30 ` Dan Cross
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='037601c37098$424eb460$b9844051@insultant.net' \
--to=boyd@insultant.net \
--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).