[Dovecot] feature or bug on delete?
RFC 3501 mentions this:
The DELETE command MUST NOT remove inferior hierarchical names.
For example, if a mailbox "foo" has an inferior "foo.bar"
(assuming "." is the hierarchy delimiter character), removing
"foo" MUST NOT remove "foo.bar". It is an error to attempt to
delete a name that has inferior hierarchical names and also has
the \Noselect mailbox name attribute (see the description of the
LIST response for more details).
It is permitted to delete a name that has inferior hierarchical
names and does not have the \Noselect mailbox name attribute. In
this case, all messages in that mailbox are removed, and the name
will acquire the \Noselect mailbox name attribute.
This is what dovecot does:
. create foo . OK Create completed. . create foo/bar . OK Create completed.
. list "" "*"
- LIST (\HasChildren) "/" "foo"
- LIST (\HasNoChildren) "/" "foo/bar" . OK List completed. (some other output removed here)
. delete foo . OK Delete completed. . list "" "*"
- LIST (\HasNoChildren) "/" "foo/bar" . OK List completed.
Reading the above section, shouldnt I be seeing a:
- LIST (\Noselect \HasChildren) "/" "foo"
Regards,
Cor
On 23.7.2005, at 15:33, Cor Bosman wrote:
RFC 3501 mentions this: .. It is permitted to delete a name that has inferior hierarchical names and does not have the \Noselect mailbox name attribute. In this case, all messages in that mailbox are removed, and the name will acquire the \Noselect mailbox name attribute. .. . list "" "*"
LIST (\HasNoChildren) "/" "foo/bar" .. Reading the above section, shouldnt I be seeing a:
LIST (\Noselect \HasChildren) "/" "foo"
If you do LIST "" %, you'll see "foo" as \NoSelect folder. Maybe the RFC tries to say that.
Anyway, I don't think there is any point to leave it as \NoSelect folder. You can already create "foo/bar" directly, and CREATE explanation doesn't require that "foo" must be shown as \NoSelect with LIST *. Besides, there is no way to create a \NoSelect folder with Maildir++.
I'll anyway ask in imap list to make sure :)
On 23.7.2005, at 16:35, Timo Sirainen wrote:
If you do LIST "" %, you'll see "foo" as \NoSelect folder. Maybe the RFC tries to say that.
Anyway, I don't think there is any point to leave it as \NoSelect folder. You can already create "foo/bar" directly, and CREATE explanation doesn't require that "foo" must be shown as \NoSelect with LIST *. Besides, there is no way to create a \NoSelect folder with Maildir++.
I'll anyway ask in imap list to make sure :)
Looks like ftp://ftp.cac.washington.edu/imap/rfc3501-errata already has corrected that.
participants (2)
-
Cor Bosman
-
Timo Sirainen