On Fri, 2 Aug 2002, LuKreme wrote:
>Andreas Aardal Hanssen wrote:
>> Sadly, courier-IMAP is still not compliant, and the author has no
>> intention of fixing it.
>Do you have any more information on this? What exactly is non compliant
>about it, etc.
>Links are fine.
>Even a hint on what to search for would be great.
I can give you one example off the top of my head :)
rfc2060 defines a set as follows:
set ::= sequence_num / (sequence_num ":" sequence_num) /
(set "," set)
;; Identifies a set of messages. For message
;; sequence numbers, these are consecutive
;; numbers from 1 to the number of messages in
;; the mailbox
;; Comma delimits individual numbers, colon
;; delimits between two numbers inclusive.
;; Example: 2,4:7,9,12:* is 2,4,5,6,7,9,12,13,
;; 14,15 for a mailbox with 15 messages.
courier-imap assumes that this means that for any a:b, a must be <= b. And
it *rejects* any requests (searches, fetches) where b > a. This is a
violation of the protocol, and the author will not fix it because he says
the rfc is broken.
Andy
--
Andreas Aardal Hanssen
