From: “L. Detweiler” <ld231782@longs.lance.colostate.edu>
To: cypherpunks@toad.com
Message Hash: 6eb9fc4d7e104c48677b5c913fb267ca26262f5cce4dfcfee057561150c64161
Message ID: <9309030539.AA16419@longs.lance.colostate.edu>
Reply To: <9309030322.AA20056@netcom5.netcom.com>
UTC Datetime: 1993-09-03 05:44:51 UTC
Raw Date: Thu, 2 Sep 93 22:44:51 PDT
From: "L. Detweiler" <ld231782@longs.lance.colostate.edu>
Date: Thu, 2 Sep 93 22:44:51 PDT
To: cypherpunks@toad.com
Subject: Re: Remailer Reliability
In-Reply-To: <9309030322.AA20056@netcom5.netcom.com>
Message-ID: <9309030539.AA16419@longs.lance.colostate.edu>
MIME-Version: 1.0
Content-Type: text/plain
tcmay@netcom.com (Timothy C. May)
>Like others, I suspect, I have to "ping" the remailers before sending
>anything, and then hope and pray they aren't taken offline for
>maintenance (or whatever) between the time I ping them and the time I
>use them for something important.
C'punks, it seems to me that the anonymous pool idea is underutilized
by the remailers. I suggest that a remailer variation be developed that
posts to an anonymous pool (some appropriate obscure newsgroup)
indicating that a message actually was sent from the final hop. The
sender can be sure the message made it if they see this posting. If
anyone wants to get even more fancy, the final remailer might also post
to the pool when the message bounced to the final address back to the remailer.
Obviously, without reliability the anonymity is worthless.
Return to September 1993
Return to “tcmay@netcom.com (Timothy C. May)”