Dave Sill writes:
> [EMAIL PROTECTED] wrote:
>
> >Someone tracked this one down and confirmed it to be a bug in Netscape
> >Messenger's IMAP client.
>
> And the "fix" is to wait for Time/Warner/CNN/AOL/Netscape to release a
> working Messenger, and get all 50 million users to install it, rather
> than accommodating the bug in the handful of courier-imap servers?
And tolerating sheer incompetence, and lack of due diligence, on the part
of commercial software vendors is how we got into this situation in the
first place.
I've already given both Messenger and Outlook Express enough slack when it
could be reasonably argued that there is a difference of opinion as to what
IMAP4rev1 is actually saying, which I consider to be the worst written RFC
I have ever read - but that's another story.
However, when there's a failure in implementing a rather clear and
unambiguous portion of the protocol, working around that particular problem
is going to get the lowest priority.
I'll fix Netscape's bugs when I have the time for it. But for now, I have
better things to do.
Until then, and I hate to say it, people should use Outlook Express's IMAP
client.
--
Sam
