On Fri, 7 Mar 2003, Kee Hinckley wrote:
Again. My mother is standing at the email kiosk in an airport. She
wants to send email to you. You've authorized one of her temporary
email messages to send email to one of your temporary email messages.
Now what?
She logs on to her ISP's Webmail system, where all of her locked
addresses are stored. Using her "normal" (to her) e-mail address, she
sends you a message over the Webmail. The ISP's server looks up the
originator address and the destination address, modifies
appropriately, and shoots it off.
Piece of cake.
Your server keeps track of everything.
Address book. Somebody needs to keep track of what email address can
send to what email address.
The server. Your server keeps track of who can send to all of your
ephemeral addresses, and my server keeps track of who can send to mine.
Do you recall the e-mail "anonymizers" of the early 1990's? You could
sign up for anonymous addresses, and the anonymizing-service would
keep track of who is who. This is a similar system.
This is typically an address book. How
does this get implemented without the use of MUA changes?
Easy. In your address book, I am
"ephem-zbhsbhbe3(_at_)roaringpenguin(_dot_)com". That's my address. No
problem.
Any mail you send to that address, from your own address, will work.
If you also have ephemeral addresses, then you need to send it out via
your server. Your server obscures your address, but that's OK,
because my server knows *you* as "ephem-zkjkejruih3(_at_)yourdomain(_dot_)com",
which is all it sees.
I am planning on implementing this, by the way; we'll see how it goes.
--
David.
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg