Summary: | Enhancement: Make use of automatically sent capability information | ||
---|---|---|---|
Product: | [Frameworks and Libraries] kio | Reporter: | Magnus Holmgren <holmgren> |
Component: | imap | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Magnus Holmgren
2006-05-08 19:40:00 UTC
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. |