Just a different flavour of the Single-User Address
idea:
Leave the sender and recipient's address untouched.
Just invent an opaque cookie which has to be presented
in the header when sending a message.
Have a Header
Mail-Cookie: ...
which presents a required cookie and a
Mail-Set-Cookie: ...
to give the recipient a cookie to use for replying.
It is the receiving MTA's private thing to evaluate the
cookie and do with it whatever it wants, like a HTTP server.
Examples uses:
- A cookie is good for anyone to send mail to a certain
address B, but is valid only for a limited amount of time.
A news posting could contain such a cookie.
A HTTP link could contain this:
<a href="mailto:..."; cookie="..."> with a cookie valid only
for an hour. You always can directly send email by just clicking
on the link, but taking the address and cookie into an address
list is useless.
- A cookie is good for sending mail from address A to address B
- A cookie is good for sending not more than n messages
- A cookie could even be sold through some kind of micro payment.
regards
Hadmut
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg