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

Header Data

From: jpp@markv.com
To: cypherpunks@toad.com
Message Hash: c05d356c6a14e06942b362690ef370c57e890092865ea574ba32c5b0404a4896
Message ID: <9402152339.aa25881@hermix.markv.com>
Reply To: N/A
UTC Datetime: 1994-02-16 07:42:57 UTC
Raw Date: Tue, 15 Feb 94 23:42:57 PST

Raw message

From: jpp@markv.com
Date: Tue, 15 Feb 94 23:42:57 PST
To: cypherpunks@toad.com
Subject: Re: RFC822 compliant, and already deployed hack for return addresses
Message-ID: <9402152339.aa25881@hermix.markv.com>
MIME-Version: 1.0
Content-Type: text/plain


  I do love to learn, I just wish it didn't have to involve pageing
through many bounce messages.  I have learned that most mailer
programs are unhappy with very long reply-to addresses.  You can rely
on about 200 to 300 chars, no more.  Too bad -- it looks like the real
easy hack won't work for too many hops.  It should work through two
remailers each with 512 bit keys, or one with 1024 bit key.

  One reply I got mentioned that author's previous experiments along
these lines.  (I am not mentioning the author's name so as to keep
their private message private.)  They mentioned trouble with the
reply-to field hack I tried; some mailers wee dropping the nice long
magic numbers.  They said the most reliable field was the subject
field.  I bet many mail agents are unhappy with long subjects too.
Hopefully they support subjects atlease as long as reply-to fields.

j'
--
		   O I am Jay Prime Positive jpp@markv.com
1250 bit fingerprint B06229 = B8 95 E0 AF 9A A2 CD A5  89 C9 F0 FE B4 3A 2C 3F
 524 bit fingerprint 2A915D = 8A 7C B9 F2 D5 46 4D ED  66 23 F1 71 DE FF 51 48
Public keys via `finger jpp@markv.com', or via email to pgp-public-keys@io.com
Your feedback is welcome directly or via my symbol JPP on hex@sea.east.sun.com

Resist the Clipper Chip, write "I oppose Clipper" to Clipper.petition@cpsr.org





Thread