From: "boyd, rounin" <boyd@sdgm.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] upas/vf
Date: Wed, 24 Sep 2003 14:48:16 +0200 [thread overview]
Message-ID: <035f01c3829a$20ebbac0$b9844051@insultant.net> (raw)
In-Reply-To: <b82b3ccd75887c959add5174634df6c3@juice.thebigchoice.com>
> >little of my system as possible, ala Boyd.
à la ...
> You should filter out viruses *before* they hit the Bayes because they can
poison
> your corpus with their "as legitimate as possible" message bodies.
i have a beer-mat / coaster / back of the envelope design to kill 'em
at the smtp level, which will 'learn' and fail 'safe'.
actually, it's currently on both sides of a an A4 page, 1 metre from me.
next prev parent reply other threads:[~2003-09-24 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-24 9:11 David Presotto
2003-09-24 10:32 ` matt
2003-09-24 12:48 ` boyd, rounin [this message]
2003-09-24 14:30 ` Joel Salomon
2003-09-24 14:57 ` boyd, rounin
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='035f01c3829a$20ebbac0$b9844051@insultant.net' \
--to=boyd@sdgm.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).