Added SPECIAL-USE to list_status #306
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some servers don't return SPECIAL-USE attributes unless they are explicitly requested in the LIST-EXTENDED command. This change makes the
list_status()
method a little bit more useful if SPECIAL-USE is included in the list of capabilities.I know that this issues a CAPABILITY command before every LIST but it seems better than having to issue a STATUS for every folder just to get the SPECIAL-USE attributes. Given that capabilities usually don't change after login it would probably make sense to cache them at session level (I can provide a patch in that sense if you like).
This change is