Red Hat Bugzilla – Bug 157425
Can not move subfolders to maildir "root" folder
Last modified: 2007-11-30 17:11:05 EST
Description of problem:
I am running a Dovecot IMAP server, with mailboxes in Maildir format.
With thunderbird I can create new folders and also drag and drop them into other
However, the move operation fails if destination is the root folder and not
another existent folder.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a folder "test1"
2. Create another folder "test2"
3. move test2 into test1: success
4. try to move back test2 to the top level
The current command did not succeed. The mail server responded: Mailbox exists..
the test2 folder is put back at the top level
I suspected Dovecot was to blame for the problem, but then I tried the same
operation with Evolution and it worked as expected.
Moreover I used ethereal to capture the IMAP connection and it recorded the
following (wrong) command:
rename: "test2.test1" "test2.test1"
with the obvious response:
NO Mailbox exists.
Confirmed presence of bug with the following:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.7.8-2
Thunderbird 1.0.2-6 (20050513) (on FC4),
Thunderbird 1.0.2-1.3.3 (on FC3)
Dovecot 0.99.14-1 (on debian server)
Also filed at bugzilla.mozilla.org:
Upstream finally fixed the bug. Are there any chance we can have the patch in a
FC5 update, until there is a new release with the fix?
Reporter, could you please reproduce this bug with the latest package for your
distribution? I cannot reproduce this with FC6 (and there is a same version of
TB on FC5 as it is on FC6). Thanks.
It is still there in my laptop with FC6 running thunderbird-22.214.171.124-1.fc6
Since upstream marked this bug with keyword "fixed1.8.1" I guess it should be
fixed in the 2.0 series, but I had no time to test this on F7.
If that is true and you want to fix it in the 1.5 series, I think the only
solution is to apply the patch they did on the Fedora SRPM
This bug has been already registered in the upstream database and we believe
that it is more approriate to let it be resolved upstream.
Red Hat will continue to track the issue in the centralized upstream bug
tracker, and will review any bug fixes that become available for consideration
in future updates.
Thank you for the bug report.