1996-10-24 - Re: Netescrow & Remailers?

Header Data

From: Matts Kallioniemi <matts@cyberpass.net>
To: cypherpunks@toad.com
Message Hash: c459f2fcef4a63057ab6705f5ca8c1155ee773f48073f3ae93707e19a3c18316
Message ID: <3.0b36.32.19961024162651.0093fab0@localhost>
Reply To: N/A
UTC Datetime: 1996-10-24 14:28:23 UTC
Raw Date: Thu, 24 Oct 1996 07:28:23 -0700 (PDT)

Raw message

From: Matts Kallioniemi <matts@cyberpass.net>
Date: Thu, 24 Oct 1996 07:28:23 -0700 (PDT)
To: cypherpunks@toad.com
Subject: Re: Netescrow & Remailers?
Message-ID: <3.0b36.32.19961024162651.0093fab0@localhost>
MIME-Version: 1.0
Content-Type: text/plain



How about this idea for improving the remailer network:

Every remailer is marked as either IN or OUT, not both. An IN remailer
accepts mail from anybody but remails only to other remailers (IN or OUT).
An OUT remailer never remails to another remailer, only to final recipient
addresses.

If an IN remailer finds itself as the last one in the chain then it picks
an OUT remailer at random to send the message through.

This way there would never be any abuse complaints on IN remailers because
they are invisible. When an OUT remailer is taken out nobody gets hurt
because OUT remailers will never be used in reply blocks.

Matts






Thread