Version: (using KDE KDE 3.5.2) Installed from: Debian testing/unstable Packages RFC 3501 section 7.2.1 states: "A server MAY send capabilities automatically, by using the CAPABILITY response code in the initial PREAUTH or OK responses, and by sending an updated CAPABILITY response code in the tagged OK response as part of a successful authentication. It is unnecessary for a client to send a separate CAPABILITY command if it recognizes these automatic capabilities." I know at least Dovecot can send such response codes. It looks like this: Connected to ittma-hohah.kibibyte.se. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS STARTTLS LOGINDISABLED] Dovecot ready.
The capability can already be evaluated and kmail actually uses this. See IMAP4Protocol::special
I believe you misunderstood me. This is just a minor optimisation that would cause the imap kioslave not to ask for capabilities right after connecting if the server includes it in its greeting, thus saving one round-trip. It has nothing to do with how the capability information can be used by Kmail et al. Before: S: * OK [CAPABILITY IMAP4Rev1 SORT STARTTLS ...] I'm ready. C: a001 CAPABILITY S: * CAPABILITY IMAP4Rev1 SORT STARTTLS ... C: a002 STARTTLS After: S: * OK [CAPABILITY IMAP4Rev1 SORT STARTTLS ...] I'm ready. C: a001 STARTTLS It would amount to adding a case for CAPABILIY in imapParser::parseResult() and changing imapParser::parseLoop() and/or IMAP4Protocol::makeLogin() so that the greeting gets parsed. It's a tad silly, although it's Right, so you mark it with WONTFIX, but I can't accept INVALID (and I reserve the right to submit a patch anyway :-).
Reassigning the bugs of the SMTP, IMAP and POP ioslaves to kdepim-bugs.
Undo autoconfirm.
kio_imap4 doesn't exist anymore.