Re: List of issues with Sieve notifications

Nigel Swinson wrote:

> > 3). Changed priority into a string containing number (currently "1", 
> > "2" and "3") (Nigel)
> :o)
>
> > Would people prefer to use "high"/"normal"/"low" instead? I though 
> > that we might want to use relational on the priority, thus it is a 
> > number for now.
> I was thinking a number which can be followed by a description.  Then 
> you can use i;ascii-numeric comparator to ignore the text if you want 
> to use the :value match type.  ie "1 Low", "2", "3 Medium", "8 Uber 
> High" etc.
> Which now makes me think we drop it entirely leaving this feature to 
> the variables extension, however I guess the reason we have it is not 
> for filtering in the Sieve domain, but rather to pass to the 
> notification mechanism,
Yes.

> in which case the content of this field is very dependant on which 
> notification mechanism that is in use.
Actually not, the content should be mapped to values expected by the 
notification mechanism.
>   Perhaps we could use mailto: as an example and show this field in 
> use to set the x-priority header?
Sure.