Re: mailserver scheme, third round

Paul Hoffman <ietf-lists@proper.com> Mon, 16 January 1995 21:33 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06503; 16 Jan 95 16:33 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa06499; 16 Jan 95 16:33 EST
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa05641; 16 Jan 95 16:33 EST
Received: (from daemon@localhost) by services.bunyip.com (8.6.9/8.6.9) id PAA03062 for uri-out; Mon, 16 Jan 1995 15:32:03 -0500
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.9/8.6.9) with SMTP id PAA03057 for <uri@services.bunyip.com>; Mon, 16 Jan 1995 15:32:00 -0500
Received: from proper.proper.com by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA10970 (mail destined for uri@services.bunyip.com) on Mon, 16 Jan 95 15:31:58 -0500
Received: from [165.227.40.37] (user37.znet.com [165.227.40.37]) by proper.proper.com (8.6.9/8.6.5) with SMTP id MAA06111; Mon, 16 Jan 1995 12:28:37 -0800
X-Sender: ietflist@proper.com
Message-Id: <ab4087e005021003d063@[165.227.40.37]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 16 Jan 1995 12:34:23 -0800
To: "Stephen R. van den Berg" <berg@pool.informatik.rwth-aachen.de>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Paul Hoffman <ietf-lists@proper.com>
Subject: Re: mailserver scheme, third round
Cc: uri@bunyip.com
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk

>Just a random thought: RFC822 does not require a space to follow the
>delimiting colon of a field name.  So, does this mean that your example
>merely describes a Subject field without a leading space?  Or does it
>mean that the mailserver URL should always cause a space to be added
>in the final message?

Neither. It means that, even though most of us are used to seeing things
like "Subject: list" in our mail clients, people should not create URLs
like <mailserver://bigstate.edu/Subject:%20list/>. The leading space (which
must be encoded) is superfluous, and may be confusing to some mail servers
who expect no leading whitespace in the Subject header.


--Paul Hoffman
--Proper Publishing