Thunderbird LSUB failed alert

[dmmincrjr]

I upgraded to version 5.0.1 and now when I connect Thunderbird clients I get the following alert at startup. "The current command did not succeed. The mail server responded: LSUB failed." When I click okay to acknowledge the alert Thunderbird functions normally. I have access to all my imap folders and can send and receive email without issue. This issue is with all computers using Thunderbird to access their mail not just one computer. I also did a fresh install of Thunderbird on a computer and encountered the problem. In opening Thunderbird and creating a log file here is where the LSUB failed error appears.

2364[37f9488]: 3906128:mail.****.com:A:CreateNewLineFromSocket: 4 OK LSUB completed

2364[37f9488]: 3906128:mail.****.com:A:SendData: 5 lsub "" "/home/*"

2364[37f9488]: ReadNextLine [stream=2b15198 nb=18 needmore=0]
2364[37f9488]: 3906128:mail.****.com:A:CreateNewLineFromSocket: 5 NO LSUB failed

2364[37f9488]: 3906128:mail.****.com:A:SendData: 6 list "" "INBOX"

2364[37f9488]: ReadNextLine [stream=2b15198 nb=37 needmore=0]
2364[37f9488]: 3906128:mail.****.com:A:CreateNewLineFromSocket: * LIST (\HasNoChildren) "/" "INBOX"

2364[37f9488]: ReadNextLine [stream=2b15198 nb=21 needmore=0]
2364[37f9488]: 3906128:mail.****.com:A:CreateNewLineFromSocket: 6 OK LIST completed

2364[37f9488]: 3906128:mail.****.com:A:SendData: 7 select "INBOX"

2364[37f9488]: ReadNextLine [stream=2b15198 nb=14 needmore=0]
2364[37f9488]: 3906128:mail.****.com:A:CreateNewLineFromSocket: * 902 EXISTS

2364[37f9488]: ReadNextLine [stream=2b15198 nb=12 needmore=0]
2364[37f9488]: 3906128:mail.****.com:A:CreateNewLineFromSocket: * 0 RECENT

I looked at the logs on the Zimbra box and cannot see where they contain anything related to this problem. I also upgraded a test box before my production box and Thunderbird connects to that without issue. The two differences are the test box does not have mail from a legacy system that I used imapsync to bring into Zimbra. I also installed zimbra proxy on the production box and not the test box by mistake. However Imap and Pop Proxy is not enabled on the production box. I also have tried accessing Zimbra with KMail and Evolution and neither program display a similar error at startup. Any suggestions as to what is causing the issue and what I can do to fix would be appreciated.

[RayzorDuff]

I am also seeing this issue on two separate 5.00 installations. The error only appears on Thunderbird clients. Has anyone done any further research into this?

[dkarp]

Yeah, it's a Thunderbird bug. See bug 23617 for more details. The workaround seems to be to (a) turn off the NAMESPACE extension in the Zimbra server and (b) contact Thunderbird and ask them to not throw up a dialog when servers return NO to requests to list all visible "other users".

[RayzorDuff]

Excellent. Thanks!

So, I didn't want to make a change that would disable folder sharing on the server. Instead, I went into the client Account Settings->Server Settings->Advanced. I set each of Personal Namespace, Public, and Other Users to "" and unchecked Allow server to override these namespaces.

This seems to work; at least for a client that is not concerned about accessing shared folders. This is what I am most concerned about immediately.

[serivo]

Hi,
After
---
zmprov mcf zimbraImapDisabledCapability NAMESPACE
zmprov mcf zimbraImapSSLDisabledCapability NAMESPACE
---
I have shared folders broken on my server.
It's production server and busines depends on this shared folders feature
Can somebody help me to undo the change as soon as possible?
Preferably without restarting mailbox service, if it's possible.

--
Sergey Ivanov.

[bobby]

If "NAMESPACE" is the only capability disabled:

>zmprov mcf zimbraImapDisabledCapability NAMESPACE
>zmprov mcf zimbraImapSSLDisabledCapability NAMESPACE

Just unset those attributes:

$ zmprov mcf zimbraImapDisabledCapability ""
$ zmprov mcf zimbraImapSSLDisabledCapability ""

You'll have to restart the mailbox app to pick this up (just like setting them in the first place):

$ zmmailboxdctl restart

[serivo]

Thanks, will do it next time, nice to know.

[marc@ion.lu]

Hi,

I also had this issue with Thunderbird on my old ZCS5 server when I moved my default domain over to my new ZCS6 server.

Other hosted accounts would get the "LSUB failed" error but continued working.

The solution was to set a new default domain in Zimbra:
> zmprov mcf zimbraDefaultDomainName default.com
solved the problem without requiring a restart.
(Note that zimbraDefaultDomainName was empty because the default domain was deleted).

I know this thread is old, but it's the first hit when googling LSUB failed.

Hope I can help someone with this.

Best regards,

MM