497337 - Enter virtual folder results in alert dialog The current command did not succeed. The mail server responded:Can't open /<blah>: not a selectable mailbox

Status: VERIFIED FIXED

(Thunderbird :: Folder and Message Lists, defect)

Description

[Wayne Mery (:wsmwk)]

with tryserver build for  Bug 474701

Enter virtual folder results in alert dialog
The current command did not succeed.  The mail server responded:Can't open /home/vseerror/mail: not a selectable mailbox

/home/vseerror/mail/ is my imap server directory in advanced settings

also get error when in virtual folder and 
* selecting view change
* doing anything in quick search

Comment 1

[David :Bienvenu]

Can you attach the relevant part of virtualFolders.dat, where the search scope for this virtual folder is defined? bug 474701 may have changed the way folders are updated for saved searches, and may be bypassing a check for no select folders - does the alert go away when you go back to a non-tryserver build?

Comment 2

[Wayne Mery (:wsmwk)]

Attachment: virtualfolders.dat

right, don't see that specific problem unless using tryserver build.


On nightly I do however get other alerts, like
 The current command did not succeed.  The mail server responded:Can't open mailbox /home/vseerror/mail/moz-misc^^abc: no such mailbox

this has been a longstanding problem

Comment 3

[Andrew Sutherland [:asuth] (he/him)]

We lost an "isServer" check.  I'll fix it.

Comment 4

[Andrew Sutherland [:asuth] (he/him)]

Added logic to DBViewWrapper.open to filter out anything that "isServer" when initializing the _underlyingFolders for a virtual folder.  _underlyingFolders is an internal-only list that is never exposed to consumers, so they should be none the wiser about the filtering going on.  Likewise, the list is never used to mutate the definition of the virtual folder, so we should not unintentionally mutate the virtual folder definitions.

added test test_virtual_folder_filters_out_servers to test_viewWrapper_virtualFolder.js

Once I spin the next build, Wayne, I'd appreciate if you could verify this problem disappears.

Comment 5

[Andrew Sutherland [:asuth] (he/him)]

Marking this RESOLVED FIXED as my fix landed with the patch.

Comment 6

[Wayne Mery (:wsmwk)]

v.fixed