User Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 Build ID: 20120215223356 Steps to reproduce: 1. Select IMAP account profile left pane (I have multiple IMAP/POP accounts in TB) 2. Right-click on profile, select New Folder 3. Fill in name "Moving" 4. Click Create Folder Actual results: The folder created appears under the #shared folder (#shared/Discards/#shared/Moving) for some reason instead of the top level. The #shared folder was explicitly NOT highlighted. For the IMAP account in question it has 38 folders. Expected results: The new (IMAP) folder should have been created as a top level private folder for the account. Not a shared folder. This appears to be a regression. The work-around was to ssh to the user account, create the file/folder, then in TB subscribe to the folder.
(In reply to Anthony Howe from comment #0) WFM. I can create top-level folders on my IMAP server. User Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 Application Build ID: 20120216022139
Can we get an imap log when you reproduce the error ? (see https://wiki.mozilla.org/MailNews:Logging for getting the log)
Component: Account Manager → Networking: IMAP
Product: Thunderbird → MailNews Core
QA Contact: account-manager → networking.imap
(In reply to Anthony Howe from comment #0) > Actual results: > The folder created appears under the #shared folder Same problem as bug 720911? See also bug 697789.
See also bug 540378, if non-personal namespace(shared/public namespace, other users namespace) is used.
Summary: New (IMAP) Folder created in wrong location. → New (IMAP) Folder created in wrong location (shared/public namespace or other users namespace is used and # is used in folder name)
Same problem encountered here with thunderbird 45.6.0 with dovecot 1:2.2.13 Attached is an imap log trace. You'll see that I tried to create AAA at the root, and it was tentatively created in #shared/mail.C770_Demonstrateur.AAA which already exists (from a precedent try). The creation of a root folder worked flawlessly from another MUA (claws mail for example)
You need to log in before you can comment on or make changes to this bug.