1993-09-03 - Re: Remailer Reliability

Header Data

From: sameer@netcom.com (Sameer Parekh)
To: ld231782@longs.lance.colostate.edu (L. Detweiler)
Message Hash: 922798b312362f41008f1108af90ba0cd1f5a54983704b00c67847792f9b867c
Message ID: <9309032129.AA02437@netcom.netcom.com>
Reply To: <9309030539.AA16419@longs.lance.colostate.edu>
UTC Datetime: 1993-09-03 21:35:07 UTC
Raw Date: Fri, 3 Sep 93 14:35:07 PDT

Raw message

From: sameer@netcom.com (Sameer Parekh)
Date: Fri, 3 Sep 93 14:35:07 PDT
To: ld231782@longs.lance.colostate.edu (L. Detweiler)
Subject: Re: Remailer Reliability
In-Reply-To: <9309030539.AA16419@longs.lance.colostate.edu>
Message-ID: <9309032129.AA02437@netcom.netcom.com>
MIME-Version: 1.0
Content-Type: text/plain


L. Detweiler said:
> C'punks, it seems to me that the anonymous pool idea is underutilized
> by the remailers. I suggest that a remailer variation be developed that
> posts to an anonymous pool (some appropriate obscure newsgroup)
> indicating that a message actually was sent from the final hop. The
> sender can be sure the message made it if they see this posting. If
> anyone wants to get even more fancy, the final remailer might also post
> to the pool when the message bounced to the final address back to the remailer.
	That definitely looks like a wise idea.
	Maybe if I can figure it out, among the writing of the
install-script I can add this little feature. Which newsgroup? Should
someone create an alt.remail? How exactly would it be implemented? I'm
thinking that simply the user would do:


::
Request-Remailing-To: sameer@netcom.com
Remail-ID: 572374237

	And the remailer would post to alt.remail:

Message with Remail-ID: 572374237 was remailed.
	Does that look good?


-- 
Sameer
sameer@netcom.com





Thread