Re: Second round for new URL scheme (mailserver)

Paul Hoffman (ietf-lists@proper.com)
Tue, 10 Jan 1995 07:48:40 -0800


Message-Id: <ab385ad30302100321b4@[165.227.40.22]>
Date: Tue, 10 Jan 1995 07:48:40 -0800
To: chrisf@sour.sw.oz.au (Christopher Fraser), uri@bunyip.com
From: ietf-lists@proper.com (Paul Hoffman)
Subject: Re: Second round for new URL scheme (mailserver)

>A useful addition would be an token which gets
>replaced with the user's email address by the browser before the mail
>gets sent.
>. . .
>I'm not sure what the best way be to encode such a token would be. Anyone
>got any ideas?

I also agree that this would be useful. Possibly we can specify an uncommon
delimiter for tokens, such as "++" before and after, that can be used or
ignored by the client. Thus, "++my-address++" could be automatically
replaced by the client when the mail message is presented to the user for
approval; if it isn't replaced, at least it will still stand out visually
and the user will (hopefully) change it before sending the message off.

On the other hand, there is no concept of such tokens in the URL spec, and
I'm not sure that this is the proper place to open that client-side
CanO'Worms. If we do, we should make it scalable to the other URL schemes.
Off the top of my head, I can see how it could also be useful in the telnet
scheme.

--Paul Hoffman
--Proper Publishing