Possible bug about the SPECIAL-USE / CREATE-SPECIAL-USE extensions
Hi all,
I've locally got Dovecot 2.2.21 (5345f22) installed on my MacBook (via homebrew) that I've been using to test my IMAP library against.
What is interesting is that even though Dovecot does not advertise CREATE-SPECIAL-USE, it supports creation of special-use folders via the "CREATE FolderName (USE (\Whatever))" syntax.
According to rfc6154, a server is supposed to advertise the CREATE-SPECIAL-USE extension if it supports this:
An IMAP server that supports this OPTIONAL feature will advertise the "CREATE-SPECIAL-USE" capability string. Clients MUST NOT use the "USE" parameter unless the server advertises the capability. Note that this capability string is different from the "SPECIAL-USE" string defined above, and a server that supports both functions MUST advertise both capability strings.
Has this been fixed in a newer version, perhaps? Or could it be a misconfiguration on my part?
Attached is my dovecot configuration (gotten via dovecot -n).
Thanks,
Jeff
On 19 Dec 2015, at 20:37, Jeff Stedfast jeff@xamarin.com wrote:
Hi all,
I've locally got Dovecot 2.2.21 (5345f22) installed on my MacBook (via homebrew) that I've been using to test my IMAP library against.
What is interesting is that even though Dovecot does not advertise CREATE-SPECIAL-USE, it supports creation of special-use folders via the "CREATE FolderName (USE (\Whatever))" syntax.
It doesn't really support that syntax yet. It just ignores all the parameters after the folder name without returning an error.
Ah, thanks for the explanation.
Btw, long time no see, Timo ;-)
Jeff
On Sat, Dec 19, 2015 at 3:05 PM, Timo Sirainen tss@iki.fi wrote:
On 19 Dec 2015, at 20:37, Jeff Stedfast jeff@xamarin.com wrote:
Hi all,
I've locally got Dovecot 2.2.21 (5345f22) installed on my MacBook (via homebrew) that I've been using to test my IMAP library against.
What is interesting is that even though Dovecot does not advertise CREATE-SPECIAL-USE, it supports creation of special-use folders via the "CREATE FolderName (USE (\Whatever))" syntax.
It doesn't really support that syntax yet. It just ignores all the parameters after the folder name without returning an error.
participants (2)
-
Jeff Stedfast
-
Timo Sirainen