Gordon Messmer writes:
On 04/01/2015 03:10 PM, Sam Varshavchik wrote: > Sounds like someone had a bad hair day. I don't know anything about it.Googling: https://bugs.kde.org/show_bug.cgi?id=338186 https://bugsfiles.kde.org/attachment.cgi?id=88636
So, what I gather from that: RFC 2060 required only EXISTS, RECENT, and UIDVALIDITY response to SELECT. RFC 3501 broke backwards compatibility, and added additional responses, but did explicitly note that clients may not rely on getting the new responses, stating: "Note that earlier versions of this protocol only required the FLAGS, EXISTS, and RECENT untagged data; consequently, client implementations SHOULD implement default behavior for missing data as discussed with the individual item." Someone wasn't paying attention, and coded an IMAP client that assumes the existence of the new responses, and then completely broke down when it didn't.
Next, someone pointed out the fact that the client should not assume that the client will get a UIDNEXT. This was explicitly documented: "If this is missing, the client can not make any assumptions about the next unique identifier value". So clients should be prepared to deal, gracefully, with the absence of the additional messages.
After this was pointed out there were two basic options: 1) Deal with it, 2) Reach out and inquire about the possibility of implementing the additional messages. The option chosen was a variation of doing #1, and then throwing an temper tantrum.
Well, I suppose that, as long as the IMAP client in question is capable of dealing with it, and is now dealing with it albeit in a somewhat juvenile manner, the issue is closed.
pgpszFQMbUNwq.pgp
Description: PGP signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
