[Dovecot] Dovecot 2.0.rc3 Capability response

[Craig Whitmore]

> 
> Doing the same on 2.0.rc3, will return only a limited set of supported
> capabilities:

Looking at the RFC.. and if dovecot is doing this then its going against
the RFC and doing it wrong. As it says "This listing of capabilities is
not dependent upon connection state or user."

http://tools.ietf.org/search/rfc1730#section-6.1.1
http://tools.ietf.org/search/rfc2060#section-6.1.1


The CAPABILITY command requests a listing of capabilities that the
      server supports.  The server MUST send a single untagged
      CAPABILITY response with "IMAP4" as the first listed capability
      before the (tagged) OK response.  This listing of capabilities is
      not dependent upon connection state or user.  It is therefore not
      necessary to issue a CAPABILITY command more than once in a
      session.


	
> 
> So what's the idea behind the change of this behavior? Is it planned to
> support different capabilities per user in the future?
> 
> The reason behind my question is, that the Open-Xchange IMAP client
> implementation relies on the presence of the ACL capability presented
> before the actual login took place.
> 
> Thanks for any clarifications.
> 
> Regards
> Christian
> 
>