# Re: mailserver scheme, third round

Paul Hoffman (ietf-lists@proper.com)
Mon, 16 Jan 1995 12:34:23 -0800

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Paul Hoffman: "Re: mailserver scheme, third round"
- Previous message: Daniel W. Connolly: "Re: mailserver scheme, third round"
- Maybe in reply to: Paul Hoffman: "mailserver scheme, third round"
- Next in thread: Stephen D. Williams: "Re: mailserver scheme, third round"
- Reply: Stephen D. Williams: "Re: mailserver scheme, third round"

    Message-Id: <ab4087e005021003d063@[165.227.40.37]>

    Date: Mon, 16 Jan 1995 12:34:23 -0800

    To: berg@pool.informatik.rwth-aachen.de (Stephen R. van den Berg)

    From: ietf-lists@proper.com (Paul Hoffman)

    Subject: Re: mailserver scheme, third round

>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

- Next message: Paul Hoffman: "Re: mailserver scheme, third round"
- Previous message: Daniel W. Connolly: "Re: mailserver scheme, third round"
- Maybe in reply to: Paul Hoffman: "mailserver scheme, third round"
- Next in thread: Stephen D. Williams: "Re: mailserver scheme, third round"
- Reply: Stephen D. Williams: "Re: mailserver scheme, third round"