Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <v04010d06b13739404960@resnick2.qualcomm.com>
In-Reply-To: <199803191959.OAA09778@CS.UTK.EDU>
References: Your message of "Thu, 19 Mar 1998 21:41:19 +0100."            
 <v04003a04b1372beb3642@[130.237.159.161]>
Date: Thu, 19 Mar 1998 15:09:31 -0600
To: Keith Moore <moore@cs.utk.edu>
From: Pete Resnick <presnick@qualcomm.com>
Subject: Re: X- fields
Cc: Jacob Palme <jpalme@dsv.su.se>,
        IETF working group on revision of mail standards <drums@cs.utk.edu>,
        Keith Moore <moore@cs.utk.edu>

On 3/19/98 at 1:59 PM -0600, Keith Moore wrote:

>> X-Priority is an example of a header field which is very commonly
>> used and which cannot be turned into a standard because of the X. It
>> would be very useful if it was turned into a standard.
>
>Really?  It's not defined anywhere.  How do I know how to interpret it?

It's defined de facto in Eudora. The field body contains "1", "2", "3",
"4", or "5" (and often contains comments in parentheses with their English
meanings: "Highest", "High", "Normal", "Low", "Lowest"). Defining it
somewhere else seems silly because it starts with "X-".

>Far better to use the RFC 1327 Priority field, which at least has a
>published definition.

Actually, no. It's not equivalent to RFC 1327's "Priority". It is like RFC
1327's "Importance" which Eudora also supports, but it is only 3 valued
instead of 5.

pr
--
Pete Resnick <mailto:presnick@qualcomm.com>
QUALCOMM Incorporated
Work: (217)337-6377 or (619)651-4478 / Fax: (217)337-1980