In Message Thu, 21 Jan 93 12:47:35 PST, Eric Messick <parallax.com!eric@netcomsv.netcom.com> writes:

The problem with this is that every site along the way has to know the final delivery address, at least of this subset of the address chain. Better to just send it directly, and add some load balancing traffic.

-eric messick

What about letting every remailer see the second to last system in the remailing process, another remailer. Other remailers would route the message around for a specified # of times +/- a small random # [users choice with a max. limit set by remailers]. The second to last remailer would recognize the last remailer from it's public key encrypted message [::Request-Remailing-To: FinalDestination] and send it on down to the last remailer which would decrypt the final remailing block using it's secret key and send the intended message to it's final destination. This would provide random remailing routes without compromising the ending not originating location. The first remailer wouldn't know if it had just received a message from a person, or another remailer. TTFN! DrZaphod [AC/DC] / [DnA][HP] [drzaphod@ncselxsi.uucp] Technicolorized