1996-05-18 - Re: The Crisis with Remailers

Header Data

From: michael shiplett <walrus@ans.net>
To: ecarp@netcom.com
Message Hash: 75453cfc10d5ea434d1eb54e30ddebf2b78c9937da5592d24fa33fde4b861ed5
Message ID: <199605171754.NAA02553@fuseki.aa.ans.net>
Reply To: <199605171622.MAA20895@dal1820.computek.net>
UTC Datetime: 1996-05-18 11:57:13 UTC
Raw Date: Sat, 18 May 1996 19:57:13 +0800

Raw message

From: michael shiplett <walrus@ans.net>
Date: Sat, 18 May 1996 19:57:13 +0800
To: ecarp@netcom.com
Subject: Re: The Crisis with Remailers
In-Reply-To: <199605171622.MAA20895@dal1820.computek.net>
Message-ID: <199605171754.NAA02553@fuseki.aa.ans.net>
MIME-Version: 1.0
Content-Type: text/plain

"ec" == Ed Carp <erc@dal1820.computek.net> writes:

ec> I think it would help tremendously if elm or pine were hacked to
ec> allow for remailing.  Even better would be some sort of dynamic
ec> remailer addressing - sendmail certainly doesn't allow for this
ec> capability. :( I think we need something similar to dynamic
ec> routing for remailers.

  I do agree extending commonly used mailers would be helpful.

  Emacs + mailcrypt (with or without MH & mh-e) already provide the
means to chain one's message through type 1 or mixmaster type 2
remailers. mailcrypt will even choose arbitrary remailer routing for
you based on information gathered from Raph Levien's remailer
list. Unforunately this is not a turnkey solution and requires more
configuration than most users probably want.


mailcrypt home page: http://cag-www.lcs.mit.edu/mailcrypt/