From: ems <oat@iinet.net.au>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] spam filtering (again)
Date: Wed, 8 Feb 2006 23:42:30 +1100 [thread overview]
Message-ID: <1139402550.24300.33.camel@heater.intranet.ebr> (raw)
In-Reply-To: <59392c44b7d21b847039ce3bd401f359@collyer.net>
On Wed, 2006-02-08 at 01:09 -0800, geoff@collyer.net wrote:
> The next step? I've got a new SMTP replacement protocol almost
> designed that should cure spam completely and not even let it across
> the wire.
djb came up with a very simple solution, http://cr.yp.to/im2000.html
I have somewhere on my to do list, to make a mail replacement, using the
concept found in im2000 (but over 9P, not http), but I am sure someone
else might be able to get there first if he wishes.
Maybe we can convince the genius, Rob Pike, to convince Google to do it,
that way such a replacement would get off the ground, very quickly, and
hyped up to off the chart numbers?
-- ems
next prev parent reply other threads:[~2006-02-08 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 8:43 Steve Simon
2006-02-08 9:09 ` geoff
2006-02-08 9:35 ` uriel
2006-02-08 9:52 ` geoff
2006-02-08 12:42 ` ems [this message]
2006-02-08 13:16 ` uriel
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=1139402550.24300.33.camel@heater.intranet.ebr \
--to=oat@iinet.net.au \
--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).