[Top] [All Lists]

Re: status of 3028bis

2005-10-20 07:18:09

Michael Haardt wrote:

On Tue, Oct 18, 2005 at 02:06:00PM -0700, Philip Guenther wrote:
In particular, there's some uncertainty
over whether comparators take octets or characters as input and how
i;octet is defined and used in the definition of other comparators.

Let "i;octet" work on characters and document the name is a misnomer.

IF someone really feels the need to specify and implement them: Introduce
Sieve extensions for a "i;binary" comparator that compares against a
string representation of binary data.  Introduce new tests "rawheader"
and "decodedheader".

I am not aware how "i;octet" is used at other places, so the above may
only fit well to Sieve.
Your suggestion make sense for header fields. But what about body extension when matching against application/* MIME part?

<Prev in Thread] Current Thread [Next in Thread>