From: s.summers1@genie.geis.com
To: cypherpunks@toad.com
Message Hash: 004145ab090c0865ec67254e922604883d5d7cddb7020938a7a114ce3354ca80
Message ID: <9307030715.AA22317@relay2.geis.com>
Reply To: N/A
UTC Datetime: 1993-07-03 07:15:22 UTC
Raw Date: Sat, 3 Jul 93 00:15:22 PDT
From: s.summers1@genie.geis.com
Date: Sat, 3 Jul 93 00:15:22 PDT
To: cypherpunks@toad.com
Subject: Junk mail/return encrypted-blo
Message-ID: <9307030715.AA22317@relay2.geis.com>
MIME-Version: 1.0
Content-Type: text/plain
From zane@genesis.mcs.com (Sameer)
>The second solution I thought of seems like it would work. When I
>create the return-address block, it can be given some sort of ID-code
>(again, like with my other idea posted, similar to the ID-code on peices
>of Digicash in Chaum's scheme) so when the vendor delivers the product,
>she sends to encrypted block to the remailer, and the remailer forwards
>the product to me, and stores the ID-code in its database (doing the
>proper one-way transformation for untraceability) so that further
>attempts to use the exact same address-block will be noticed and not
>delivered.
Why not just include an Expire: header in the encrypted block, after
which the remailer would just junk any mail sent with that return address?
Return to July 1993
Return to “s.summers1@genie.geis.com”
1993-07-03 (Sat, 3 Jul 93 00:15:22 PDT) - Junk mail/return encrypted-blo - s.summers1@genie.geis.com