cryptoanarchy.wiki

Arise, you have nothing to lose but your barbed wire fences!

1996-05-19 - None

Header Data

From: Yap Remailer <remailer@yap.pactitle.com>
To: cypherpunks@toad.com
Message Hash: 9e956db2782b5592ebed063978c4f5d84ebf125a9bac44ea20fc9e5bb8855685
Message ID: <199605181915.MAA13072@yap.pactitle.com>
Reply To: <199605171754.NAA02553@fuseki.aa.ans.net>
UTC Datetime: 1996-05-19 00:48:20 UTC
Raw Date: Sun, 19 May 1996 08:48:20 +0800

Raw message

From: Yap Remailer <remailer@yap.pactitle.com>
Date: Sun, 19 May 1996 08:48:20 +0800
To: cypherpunks@toad.com
Subject: None
In-Reply-To: <199605171754.NAA02553@fuseki.aa.ans.net>
Message-ID: <199605181915.MAA13072@yap.pactitle.com>
MIME-Version: 1.0
Content-Type: text/plain


> From: michael shiplett <walrus@ans.net>
> Date: Fri, 17 May 1996 13:54:51 -0400
> 
>   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.
> 
> michael

Mailcrypt support for type 2 remailers doesn't really work very well.
You can't specify more than one recipient.  You can't post to a
newsgroup with the "post: news.group" destination.  And somehow not
all the right headers end up making it into the next message.

A better emacs interface to mixmaster remailers is definitely needed.

Thread