From: chrisf@sour.sw.oz.au (Christopher Fraser)
Message-Id: <199501100340.AA11196@sour.sw.oz.au>
Subject: Re: Second round for new URL scheme (mailserver)
To: uri@bunyip.com
Date: Tue, 10 Jan 1995 14:40:37 +1100 (EST)
In-Reply-To: <ab3775cf000210038cd0@DialupEudora> from "Paul Hoffman" at Jan 9, 95 04:16:41 pm
But I thought Paul Hoffman said:
> [ ... ]
> The "mailserver" URL has the form:
>
> mailserver:<rfc822-addr-spec>/<subject>/<body>/[<other-headers>]
>
> Client software would prepare a mail message with the <subject> text as the
> subject and the <body> text as the body of the message.
It looks good to me. A useful addition would be an token which gets
replaced with the user's email address by the browser before the mail
gets sent. Why would this be useful? I can think of three reasons:
* Some people like to have mailing-list traffic delivered to a different
email address to their usual one.
* Some mailing-list software likes the senders address to be included in
the subject or body of the message.
* Some browsers run on machines other than where mail should be delivered
to (uncommon, I know).
I'm not sure what the best way be to encode such a token would be. Anyone
got any ideas?
Cheers,
-- Christopher Fraser ``First time surrealists are often confused by the chrisf@sw.oz.au similarities between fish and telephones.''