Re: mailserver scheme, third round

Stephen R. van den Berg (berg@pool.informatik.rwth-aachen.de)
Mon, 16 Jan 1995 20:37:39 +0100


Message-Id: <9501161937.AA21929@tabaqui>
From: berg@pool.informatik.rwth-aachen.de (Stephen R. van den Berg)
Date: Mon, 16 Jan 1995 20:37:39 +0100
In-Reply-To: Paul Hoffman's message as of 1995 Jan 14 Sat 20:46.
       <ab3e57c407021003efea@[165.227.40.13]>
To: ietf-lists@proper.com (Paul Hoffman), uri@bunyip.com
Subject: Re: mailserver scheme, third round

Paul Hoffman <ietf-lists@proper.com> wrote:
>     mailserver:<rfc822-addr-spec>/*[<header>/]/<body>

>Headers are given in RFC822 format, and it is likely (and probably
>preferable) that only a "Subject:" header be included. Headers are given
>without spaces after them, such as "Subject:current-issue".

>The body text may span more than one line. Any "/" character in the body
>should be interpreted by the mail client as a CRLF sequence when
>translating a URL to a mail message.

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?

Not that this is likely to cause much problems, it's just that the
formulation is not quite clear on this point.

-- 
Sincerely,                                  berg@pool.informatik.rwth-aachen.de
           Stephen R. van den Berg (AKA BuGless).

Up your accumulator.