Re: Predraft of a new URL scheme: mailmsg

Larry Masinter (masinter@parc.xerox.com)
Tue, 3 Jan 1995 17:31:46 PST


To: raisch@internet.com
Cc: uri@bunyip.com, ietf-lists@proper.com
In-Reply-To: raisch@internet.com's message of Tue, 3 Jan 1995 16:34:43 -0800 <95Jan3.163456pst.2765@golden.parc.xerox.com>
Subject: Re: Predraft of a new URL scheme: mailmsg
From: Larry Masinter <masinter@parc.xerox.com>
Message-Id: <95Jan3.173159pst.2760@golden.parc.xerox.com>
Date: Tue, 3 Jan 1995 17:31:46 PST

I think we've been over this, and it's the main reason for the
'security considerations' section.

We already had this with

gopher://whitehouse.gov:25/HELO%20host.com%0cMAIL%20from:<sucka>RCPT%20to:<president>%0f...

etc. case. URL interpreting agents need to be careful, and
descriptions of URL schemes need to point out all of the pitfalls so
that URL interpreting agents don't fall into them.