Re: imap/2837: MYRIGHTS not understood by Mirapoint IMAP4PROXY
The following reply was made to PR imap/2837; it has been noted by GNATS.
From: Kyle Wheeler <kyle-mutt-dev@xxxxxxxxxxxxxx>
To: Mutt Developers <mutt-dev@xxxxxxxx>
Cc: bug-any@xxxxxxxxxxxxx
Subject: Re: imap/2837: MYRIGHTS not understood by Mirapoint IMAP4PROXY
3.5.8-GR server
Date: Thu, 8 Mar 2007 12:11:20 -0700
On Thursday, March 8 at 07:25 PM, quoth Christoph Berg:
>I think the fact that MYRIGHTS is not understood by the imap server I
>connect to causes mutt to think my folders are read-only.
For what it's worth, in this case, the IMAP server is broken. What
causes mutt to think that it can use the MYRIGHTS command is that the
server *claims* to be able to understand it, and then later
contradicts itself.
>4> a0000 CAPABILITY^M
>4< * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS
Notice that the server returned that one of it's capabilities is ACL.
According both to RFC 4314 (which defines the ACL capability) and RFC
2086 (which was obsoleted by 4313), any server which claims it
supports the ACL capability MUST support the commands SETACL,
DELETEACL, GETACL, LISTRIGHTS, and MYRIGHTS.
>I just noticed by connecting from telnet that the CAPABILITY results
>are different before and after LOGIN.
>
>Before:
>
>CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS
>
>After (note there is no ACL capability here):
>
>CAPABILITY IMAP4 IMAP4rev1 IDLE LOGIN-REFERRALS MAILBOX-REFERRALS
>NAMESPACE LITERAL+ UIDPLUS CHILDREN
This is, well, stupid. Not only do they claim ACL support, but QUOTA
support as well.
The patch you sent works around this, but you really ought to contact
the authors of the IMAP server and tell them to fix their broken
server. They shouldn't claim to support capabilities that they do not
actually support, no matter whether you're authenticated or not.
~Kyle
--
Having a family is like having a bowling alley installed in your
brain.
-- Martin Mull