[Dovecot] SELECT: Bug in untagged response
Dovecot 2.2.5
In selected state:
C: 1 SELECT -/# S: 1 NO Mailbox name is not valid mUTF-7 S: * OK [CLOSED] Previous mailbox closed.
I can verify that this only seems to happen when the mailbox name is
incorrect mUTF-7. Things work fine if I access a non-existent mailbox:
C: 1 SELECT non-existent-mailbox S: * OK [CLOSED] Previous mailbox closed. S: a NO Mailbox doesn't exist: non-existent-mailbox
FYI: Switching to Dave C's workaround discussed here --
http://mailman2.u.washington.edu/pipermail/imap-protocol/2005-September/0000... -- regarding servers that don't support UNSELECT. This would normally never happen on Dovecot since it supports UNSELECT; I'm intentionally ignoring that capability for testing
purposes.
I'm not pipelining a CLOSE with the above SELECT command, like Dave
suggests, because the likelihood this SELECT will be successful is
about zero and I'd rather avoid a BAD response to a CLOSE command,
since it is plausible that a server could issue a CLIENTBUG response
for a client that is trying to CLOSE a mailbox in Authenticated State.
(Granted, a server could also plausibly issue a CLIENTBUG for
identifying a mailbox in incorrect mUTF-7 also, but whatever.)
michael
On 14.9.2013, at 1.37, Michael M Slusarz <slusarz@curecanti.org> wrote:
In selected state:
C: 1 SELECT -/# S: 1 NO Mailbox name is not valid mUTF-7 S: * OK [CLOSED] Previous mailbox closed.
I can verify that this only seems to happen when the mailbox name is incorrect mUTF-7. Things work fine if I access a non-existent mailbox:
C: 1 SELECT non-existent-mailbox S: * OK [CLOSED] Previous mailbox closed. S: a NO Mailbox doesn't exist: non-existent-mailbox
participants (2)
-
Michael M Slusarz
-
Timo Sirainen