Message-Id: <m0rTufC-0009v9C@sdwsys>
From: sdw@lig.net (Stephen D. Williams)
Subject: Re: mailserver scheme, third round
To: ietf-lists@proper.com (Paul Hoffman)
Date: Mon, 16 Jan 1995 16:52:14 +0000 (GMT)
In-Reply-To: <ab4087e005021003d063@[165.227.40.37]> from "Paul Hoffman" at Jan 16, 95 12:34:23 pm
>
> >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?
I agree, but don't have time to look it up today, that the spec requires
a space after the :... Almost positive, and I've seen parsing code
that insists on it. Just as the blank line delimits the header,
the space delimits the tag. (Technically, the colon does, and I
wouldn't want to try having a : in the tag, but the space further
delimits it.)
Why reply if I don't have time to get the spec? I don't know...
> 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
>
>
>
-- Stephen D. Williams 25Feb1965 VW,OH sdw@lig.net http://www.lig.net/sdw Senior Consultant 510.503.9227 CA Page 513.496.5223 OH Page BA Aug94-Dec95 OO R&D AI:NN/ES crypto By Buggy: 2464 Rosina Dr., Miamisburg, OH 45342-6430 Firewalls/WWW servers ICBM: 39 38 34N 84 17 12W home, 37 58 41N 122 01 48W work Pres.: Concinnous Consulting,Inc.;SDW Systems;Local Internet Gateway Co.29Nov94