[Imap-protocol] BODY.PEEK[section]<origin.size> FETCH response

[Mark Crispin]

On Tue, 1 Nov 2011, Bron Gondwana wrote:

>> FWIW, I always considered the implementation of string searching to be

>> implementation dependent. The only requirement was that simple

>> case-independent substring is recognized as compliant. I never intended

>> that a server be forbidden from implementing a smarter search (e.g.,

>> fuzzy) that returns more matching messages.

> Interesting.  That makes me feel a bit more comfortable about ignoring the

> full RFC 5051 i;unicode-casemap on searches, and only using it for sort.


You can not do that and claim compliance with RFC 5255.

RFC 5255 explicitly requires that you apply i;unicode-casemap in searches
as part of level 1 compliance.

If you do not claim RFC 5255 compliance then there is no particular reason
to implement i;unicode-casemap at all.

However, as far as I know, however, Cyrus always implemented a variant of
it from its inception; so you would actually be removing an aspect of it
that was in there from the onset. That is probably not a good idea.

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.