From: Wes Kussmaul <wes@village.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] stubbing
Date: Fri, 7 Oct 2005 11:07:17 -0400 [thread overview]
Message-ID: <43468F25.9080007@village.com> (raw)
In-Reply-To: <434689BF.7080700@anvil.com>
Dave Lukes wrote:
> I'm sure we'd all like to hear of a spam-protection system which isn't a
> PITA to administer
> and which actually delivers the message before the recipient dies of old
> age:
> greylisting is too slow for our business.
> Sadly, in reality, I suspect that what we have here (spamassassin and
> blacklists up the eyeballs)
> is about as good as it gets:
> evidence to the contrary gratefully received.
Evidence to the contrary:
Premise: A reliable, large-scale, deployable PKI with reliable identity
credentials that fortify rather than erode privacy will solve most of
the spam problem.
Relevant cliche': "It's been tried many times. A reliable, large-scale,
deployable PKI will never happen."
Exhibit A: Skype is a massive, working, worldwide, trouble-free PKI that
was just bought by a company (eBay) that desperately needs the kind of
transactional authenticity/integrity that a PKI like Skype can provide.
Exhibit B (to be introduced shortly; will demonstrate that reliable
identities, while labor intensive, are obtainable)
You're welcome.
Wes
The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s)
and may contain confidential or privileged information. If you are not
the intended recipient, please notify attorney Mort Hapless at Vulner,
Exposed & Wideopen LLP immediately at either (781) 647-7178, or at
ohoh@vulex.com, and destroy all copies of this message and any
attachments. No, really. Really. Listen, we mean it! Hey, if you don’t
stop reading that confidential stuff about our client you’re in big
trouble. OK, we’re the ones in trouble but we’ll find a way to go after
you, or at least we think we may be able to. Look, we’re begging you.
Just click the delete button and move on to a message that concerns you,
OK? Please?? We'll buy you lunch...
next prev parent reply other threads:[~2005-10-07 15:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 2:53 Jack Johnson
2005-10-06 4:14 ` Russ Cox
2005-10-06 9:01 ` Steve Simon
2005-10-07 0:14 ` C H Forsyth
2005-10-07 14:44 ` Dave Lukes
2005-10-07 15:04 ` Charles Forsyth
2005-10-07 15:26 ` Ronald G Minnich
2005-10-07 15:46 ` Russ Cox
2005-10-07 15:55 ` Wes Kussmaul
2005-10-07 15:07 ` Wes Kussmaul [this message]
2005-10-08 22:57 ` Dave Lukes
2005-10-08 23:08 ` Wes Kussmaul
2005-10-08 23:37 ` Dave Lukes
2005-10-09 0:31 ` Wes Kussmaul
2005-10-09 2:00 ` erik quanstrom
2005-10-09 4:21 ` Wes Kussmaul
2005-10-09 16:53 ` lucio
[not found] <4349587F.8070200@village.com>
2005-10-12 19:11 ` lucio
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=43468F25.9080007@village.com \
--to=wes@village.com \
--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).