* OK Merak 7.4.5 IMAP4rev1 Thu, 08 Jul 2004 11:24:27 +0300
a login test1 123456
a OK LOGIN Completed
b select inbox
* FLAGS (\Seen \Answered \Flagged \Deleted \Draft \Recent)
* 1 EXISTS
* 0 RECENT
* OK [UNSEEN 0]
* OK [UIDVALIDITY 818058273] UIDs valid
* OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Draft \Deleted)]
b OK [READ-WRITE] SELECT Completed
U100 uid fetch 383 (UID BODY.PEEK[1]<0.20> RFC822.HEADER)
* 1 FETCH (UID 383 BODY[1]<0> {20}
=20
=20
Liran Poll RFC822.HEADER<0> {20}
Received: from fiat.)
U100 OK UID FETCH Completed

Make a quick perusal of this fragment of an IMAP session and the server's misbehavior should be very obvious. The protocol just does not allow for the partial fetch of an RFC822.HEADER.

That, in my view, is not the real problem though. As a server developer myself, I am inclined to be extremely forgiving of server bugs. The problem, as I see it, is that when a colleague of mine reported the problem to the vendor, Merak, the response that came back refused to acknowledge any error but apparently attempted to justify the behavior citing RFC 1370 ("Applicability Statement for OSPF"), a document that has nothing whatsoever to do with IMAP.

Now, this is not Courier we are talking about. What sort of reputation does Merak have? Does anyone connected with Merak read this mailing list?

Pete Maclean

--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html
-----------------------------------------------------------------




Reply via email to