diff options
| author | Matthew Barnes <mbarnes@redhat.com> | 2013-09-03 21:35:01 -0400 |
|---|---|---|
| committer | Matthew Barnes <mbarnes@redhat.com> | 2013-09-12 13:00:28 -0400 |
| commit | da8a772363afb9a1bbcdcaf038a376fcf399b303 (patch) | |
| tree | cc137c8f2a80756c60957f779d73f8f479ebed0f /camel/camel-imapx-utils.c | |
| parent | ca5a3e78c945c6712a4e1daa2e2ad429e2467593 (diff) | |
| download | evolution-data-server-da8a772363afb9a1bbcdcaf038a376fcf399b303.tar.gz | |
CamelIMAPXServer: Support the SPECIAL-USE capability.
http://tools.ietf.org/html/rfc6154
Camel does not yet provide an API for applications to utilize this
information, but we can still capture it in a CamelIMAPXMailbox.
I'm still pondering a suitable application-facing API for this. I'd
prefer to avoid stuffing this into CamelFolderInfoFlags if I can, as
Camel already overuses / abuses flag values as it is.
Diffstat (limited to 'camel/camel-imapx-utils.c')
| -rw-r--r-- | camel/camel-imapx-utils.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/camel/camel-imapx-utils.c b/camel/camel-imapx-utils.c index c49cafb49..6ba770f28 100644 --- a/camel/camel-imapx-utils.c +++ b/camel/camel-imapx-utils.c @@ -423,7 +423,8 @@ struct { { "LIST-STATUS", IMAPX_CAPABILITY_LIST_STATUS }, { "QUOTA", IMAPX_CAPABILITY_QUOTA }, { "MOVE", IMAPX_CAPABILITY_MOVE }, - { "NOTIFY", IMAPX_CAPABILITY_NOTIFY } + { "NOTIFY", IMAPX_CAPABILITY_NOTIFY }, + { "SPECIAL-USE", IMAPX_CAPABILITY_SPECIAL_USE } }; static GMutex capa_htable_lock; /* capabilities lookup table lock */ |