You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Steve Brewin (JIRA)" <se...@james.apache.org> on 2015/08/18 19:09:45 UTC
[jira] [Updated] (IMAP-380) Implement IMAP LIST Extension for
Special-Use Mailboxes, RFC 6154
[ https://issues.apache.org/jira/browse/IMAP-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Brewin updated IMAP-380:
------------------------------
Description:
>From the RFC 6154:
"Some IMAP message stores include special-use mailboxes, such as those
used to hold draft messages or sent messages. Many mail clients
allow users to specify where draft or sent messages should be put,
but configuring them requires that the user know which mailboxes the
server has set aside for these purposes."
Some mail clients, notably Microsoft Outlook 2013 and later, require RFC 6154 support to function correctly. RFC 6154 is a standardisation of Google's XLIST capability that also extends the CREATE command to allow the designation of special use mailboxes.
Some work is already committed to support XLIST. An implementer might use this as a starting point as RFC 6154 and XLIST are very similar. The XLIST work is incomplete; the CAPABILITY command does not announce it and there is no provision for designating a mailbox as special.
After implementing RFC 6154 fully enabling XLIST support would be trivial, though most mail clients and even Google's GMail have moved on to the official RFC.
was:
>From the RFC 6154:
"Some IMAP message stores include special-use mailboxes, such as those
used to hold draft messages or sent messages. Many mail clients
allow users to specify where draft or sent messages should be put,
but configuring them requires that the user know which mailboxes the
server has set aside for these purposes."
Some mail clients, notably Microsoft Outlook 2013 and later, require RFC 6154 support to function correctly. RFC 6154 is a standardisation of Google's XLIST capability that also extends the CREATE command to allow the designation of special use mailboxes.
Some work is already committed to support XLIST. An implementer might use this as a starting point as RFC 6154 and XLIST are very similar. The work is incomplete; the CAPABILITY command does not announce it and there is no provision for designating a mailbox as special.
After implementing RFC 6154 fully enabling XLIST support would be trivial, though most mail clients and even Google's GMail have moved on to the official RFC.
> Implement IMAP LIST Extension for Special-Use Mailboxes, RFC 6154
> -----------------------------------------------------------------
>
> Key: IMAP-380
> URL: https://issues.apache.org/jira/browse/IMAP-380
> Project: James Imap
> Issue Type: New Feature
> Affects Versions: 0.3
> Reporter: Steve Brewin
>
> From the RFC 6154:
> "Some IMAP message stores include special-use mailboxes, such as those
> used to hold draft messages or sent messages. Many mail clients
> allow users to specify where draft or sent messages should be put,
> but configuring them requires that the user know which mailboxes the
> server has set aside for these purposes."
> Some mail clients, notably Microsoft Outlook 2013 and later, require RFC 6154 support to function correctly. RFC 6154 is a standardisation of Google's XLIST capability that also extends the CREATE command to allow the designation of special use mailboxes.
> Some work is already committed to support XLIST. An implementer might use this as a starting point as RFC 6154 and XLIST are very similar. The XLIST work is incomplete; the CAPABILITY command does not announce it and there is no provision for designating a mailbox as special.
> After implementing RFC 6154 fully enabling XLIST support would be trivial, though most mail clients and even Google's GMail have moved on to the official RFC.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org