From: Dave Lukes <davel@anvil.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] stubbing
Date: Sat, 8 Oct 2005 23:57:07 +0100 [thread overview]
Message-ID: <8e66d19bc2b4abacfe98ac5a29e70002@anvil.com> (raw)
In-Reply-To: <43468F25.9080007@village.com>
> 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.
... and this helps my current spam problem how?
DaveL
next prev parent reply other threads:[~2005-10-08 22:57 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
2005-10-08 22:57 ` Dave Lukes [this message]
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=8e66d19bc2b4abacfe98ac5a29e70002@anvil.com \
--to=davel@anvil.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).