Hi Stephen, I hadn't thought it could be the cause, but when you mention it, it could be possible. Essentially, a STATUS command is embedded in the LIST to try and be more efficient, and it could be Thunderbird is trying that. Although, a sensible client should then see the error and run distinct commands to achieve the same effect. I don't know enough about what Thunderbird is doing when the problem happens to say for sure.
For the automatic upgrade, the only issue is the adding the extension as that requires full database privilege, so may be needed to be done manually. This is what adds the UUID type and associated functions. I thought about just manipulating the mailbox ID (to return it to look like a uuid) but in the end decided a proper uuid was likely a better solution. In theory you could have another 'lazy' IMAP server just manipulating a mailbox number and end up with a collision on your client with unpredictable results. Using a uuid at the start avoids this risk. Jim On 10/06/2016 23:41, Stephen R. van den Berg wrote: > NSS Ltd wrote: >> I've just updated to the latest git master and see a number of back-off >> due to imap syntax error messages. >> The offending command seems to be : >> list "" "*" return (status (x-guid) children) >> And the 'status' seems to be the problem. >> 114 BAD Unknown return option: status > Is this related to my Thunderbird problem about Status being temporarily > reverted? > Arnt? > > I'll try this patch, if it works I'll be able to check it into the repository > (unless Arnt vetoes it). > The only thing that needs to be properly verified is that the automatic > database upgrade/downgrade logic takes into account your changes to > the database structure.
