Hadmut Danisch wrote:
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.
Such cookies would be inferior, I believe, to a system such as
Single-user addresses since they require both sender and receiver to
have mail systems that understand the additional header fields. On the
other hand, handling of a single-user address of the form
"username+signature(_at_)example(_dot_)com" is something that can be deployed
immediately by any mail recipient who has a mail server capable of
ignoring the signature part when determing who the mail is destined for.
Thus, if you use sendmail for SMTP, or you use Earthlink or a number of
other mail providers, you can create and use single-user addresses NOW.
All you have to do is put the single-user email address into the
"reply-to" and "From" fields of your messages.
There are all sorts of things that can be done if we are free to
redesign the mail protocols. For instance, we could get into the whole
PKI issue... However, the reality is that such efforts will take a great
deal of time to design and they will take even longer to propogate
through the internet. Thus, it makes sense to consider methods that will
result in minimal disruption to the existing protocols. The single user
address (especially if based on the "+" convention) allows the method to
be used with NO modifications to existing protocols.
bob wyman
-----Original Message-----
From: asrg-admin(_at_)ietf(_dot_)org [mailto:asrg-admin(_at_)ietf(_dot_)org] On
Behalf Of
Hadmut Danisch
Sent: Monday, March 03, 2003 3:43 PM
To: asrg(_at_)ietf(_dot_)org
Subject: [Asrg] Mail Cookies Was: Single-User Addresses
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
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg