This page was mutated from its original content to reduce and change some links that could confuse integrity.
This was an html rendering of an original raw plaintext email numbered 004916.
Junk mail/return encrypted-blo
s.summers1 at genie.geis.com
s.summers1 at genie.geis.com
Sat Jul 3 00:15:22 PDT 1993
- Previous message: Science News article request
- Next message: (fwd) GIFs--Now it can be told
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
>From zane at 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?
- Previous message: Science News article request
- Next message: (fwd) GIFs--Now it can be told
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the cypherpunks-legacy mailing list