Re: RE[2]: mailto URLs
Prabhat Keni <pkeni@netscape.com> Mon, 29 January 1996 18:57 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa28660;
29 Jan 96 13:57 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id ab28656;
29 Jan 96 13:57 EST
Received: from list.cren.net by CNRI.Reston.VA.US id aa12895;
29 Jan 96 13:57 EST
Received: from localhost (localhost [127.0.0.1]) by list.cren.net
(8.6.12/8.6.12) with SMTP id NAA21693; Mon, 29 Jan 1996 13:30:47 -0500
Received: from netscape.com (starfish.netscape.com [205.217.237.33]) by
list.cren.net (8.6.12/8.6.12) with ESMTP id NAA21620 for
<ietf-822@list.cren.net>; Mon, 29 Jan 1996 13:29:00 -0500
Received: from iapp9.mcom.com (pkeni@iapp9.mcom.com [205.217.229.34]) by
netscape.com (8.6.12/8.6.9) with ESMTP id KAA08431;
Mon, 29 Jan 1996 10:27:03 -0800
Message-Id: <199601291827.KAA08431@netscape.com>
Date: Mon, 29 Jan 1996 10:25:33 -0800
X-Orig-Sender: owner-ietf-822@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Prabhat Keni <pkeni@netscape.com>
To: Mike Braca <mb@ebt.com>
Cc: "Dr. Mark K. Joseph" <izzy@aac.twg.com>, masinter@parc.xerox.com,
timbl@www0.cern.ch, mpm@boombox.micro.umn.edu, ietf-822@list.cren.net,
bhk@aac.twg.com, jwz@netscape.com
Subject: Re: RE[2]: mailto URLs
In-Reply-To: Your message of "Mon, 08 Jan 1996 16:56:05 EST."
<30F192F5.6162@ebt.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: pkeni@iapp9.mcom.com
X-Listprocessor-Version: 8.0(dev) -- ListProcessor by CREN
Mike Braca <mb@ebt.com> writes: > Hmmm, I just found out that Netscape is sending the headers through as a > query, with '?'. I dislike that also, but not as much as '#'. At least > '?' has a history of being mangled. > mailto:mb@ebt.com?SUBJECT=foo;CC=bar Following is what Netscape does today. Its similar in spirit to the proposal which started this discussion with the following differences: o covers more headers. o Parses mailbox instead of addr-spec, so one could specify full names in addition to bare addresses. o Multiple addresses are allowed. o There's no mechanism to specify body. Although, it'd be nice to be able to do that. Quote from an internal email from a colleague: > The syntax goes something like > > URL := 'mailto:' [ ADDRS ] [ HEADERS ] > ADDRS := [ ADDR [ ',' ADDR ]* ] > ADDR := <RFC822 address, hex-encoded if necessary> > HEADERS := '?' HNAME '=' HVALUE [ '&' HNAME '=' HVALUE ] > HNAME := <a mail header name; currently we only support those > headers which you can edit in a mail composition window, > but it would be sensible to allow other headers as well > (with an exclusion list of "dangerous" headers.)> > HVALUE := <contents of the header, hex-encoded if necessary> > > This allows a URL to initialize the contents of a mail composition > window; for example, you could put a URL in a document like > > <A HREF="mailto:jwz@netscape.com?subject=cool%20page%21&cc=someone@elsewhere.com"> > > and when the user clicked on it, there would be a default subject > waiting for them. > > We also support this syntax when using a mailto as the POST address > of a form submission; but in that case, we allow all headers, even > unknown ones, to be generated, except for "dangerous" headers. > These are the headers that form submissions cannot set or override > the default values of: > > Apparently-To > BCC > Content-Encoding > Content-Transfer-Encoding > Content-Type > Date > Distribution > FCC > Followup-To > From > MIME-Version > Message-ID > Newsgroups > Organization > Reply-To > Sender > X-Mozilla-Status > X-UIDL > XRef > > For example, to have a form which sent mail with a different > subject, and some unknown header, one could do this: > > <FORM METHOD=POST > ENCTYPE=text/plain > ACTION="mailto:no-such-address?Subject=neato&X-Random-Header=yow"> > <INPUT TYPE=TEXT NAME=disposition VALUE="hey, cool"> > <INPUT TYPE=submit VALUE="Send Mail"> > </FORM> -- Prabhat Keni.
- mailto URLs Dr. Mark K. Joseph
- Re: mailto URLs Mike Braca
- RE[2]: mailto URLs Dr. Mark K. Joseph
- Re: RE[2]: mailto URLs Mike Braca
- Re: RE[2]: mailto URLs Prabhat Keni
- Re: RE[2]: mailto URLs Larry Masinter
- Re: RE[2]: mailto URLs Harald.T.Alvestrand
- Re: RE[2]: mailto URLs Jamie Zawinski
- Re: RE[2]: mailto URLs Harald.T.Alvestrand