1994-02-16 - Re: RFC822 compliant, and already deployed hack for return addresses

Header Data

From: “Jon ‘Iain’ Boone” <boone@psc.edu>
To: “This is the place to put the very long magic numbers which represent a return address encrypted with the actual recipients public key which the recipient could decrypt and use as further remailing instructions this much text would only represent two hops so there may be buffer limits which multiple hop messages would overflow thus preventing the deli, very of the message but at least the there is a good chance your mail client will jpp@markv.com>
Message Hash: fd87634c962dc1a5a1414651f166b681c63c0cf5d8f3905fb167cf8a26e4c4cd
Message ID: <9402161146.AA16805@igi.psc.edu>
Reply To: <9402152047.aa11630@hermix.markv.com>
UTC Datetime: 1994-02-16 11:50:14 UTC
Raw Date: Wed, 16 Feb 94 03:50:14 PST

Raw message

From: "Jon 'Iain' Boone" <boone@psc.edu>
Date: Wed, 16 Feb 94 03:50:14 PST
To: "This is the place to put the very long magic numbers which represent a return address encrypted with the actual recipients public key which the recipient could decrypt and use as further remailing instructions this much text would only represent two hops so there may be buffer limits which multiple hop messages would overflow thus preventing the deli,       very of the message but at least the there is a good chance your mail client will jpp@markv.com>
Subject: Re: RFC822 compliant, and already deployed hack for return addresses
In-Reply-To: <9402152047.aa11630@hermix.markv.com>
Message-ID: <9402161146.AA16805@igi.psc.edu>
MIME-Version: 1.0
Content-Type: text/plain



jpp@markv.com  writes:
>
>   Go ahead, hit 'r' and see what you get.  How many of you get the
> whole verbose reply-to field?

  MH yields the Reply-To: field in its entirety.

 Jon Boone | PSC Networking | boone@psc.edu | (412) 268-6959 | PGP Key # B75699
 PGP Public Key fingerprint =  23 59 EC 91 47 A6 E3 92  9E A8 96 6A D9 27 C9 6C





Thread