External IMAP account errors

[Vladimir]

I have a strange error with external IMAP accounts. Some external imap accounts fail with a user error which matches the one in my logs and is included bellow. I even have two users subscribed to mailboxes in the same external server and one sees this error and one does not. Has anyone seen this before?

I had the user nuke the account and recreate it and then they got the second error included.

2008-04-16 15:20:38,004 INFO [btpool0-62] [name=jscalf@zt2.rutgers.edu;mid=14;ip=165.230.78.1 58;ua=ZimbraWebClient - FF2.
0 (Linux)/5.0.4_GA_2101.UBUNTU6;ds=Andromeda;] datasource - Importing data.
2008-04-16 15:20:38,804 INFO [btpool0-62] [name=jscalf@zt2.rutgers.edu;mid=14;ip=165.230.78.1 58;ua=ZimbraWebClient - FF2.
0 (Linux)/5.0.4_GA_2101.UBUNTU6;ds=Andromeda;] SoapEngine - handler exception
com.zimbra.common.service.ServiceException: system failure: A4 NO Mailbox does not exist, or must be subscribed to.
ExceptionId:btpool0-62:1208373638804:4945c3377364cbbf
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:253)
at com.zimbra.cs.datasource.ImapImport.importData(Ima pImport.java:369)
at com.zimbra.cs.datasource.DataSourceManager.importD ata(DataSourceManager.java:148)
at com.zimbra.cs.service.mail.ImportData.handle(Impor tData.java:62)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:391)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:250)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:156)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:266)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)
Caused by: javax.mail.MessagingException: A4 NO Mailbox does not exist, or must be subscribed to.;
nested exception is:
com.sun.mail.iap.CommandFailedException: A4 NO Mailbox does not exist, or must be subscribed to.
at com.sun.mail.imap.IMAPFolder.getUIDValidity(IMAPFo lder.java:1730)
at com.zimbra.cs.datasource.ImapImport.importData(Ima pImport.java:187)
... 32 more
Caused by: com.sun.mail.iap.CommandFailedException: A4 NO Mailbox does not exist, or must be subscribed to.
at com.sun.mail.iap.Protocol.handleResult(Protocol.ja va:328)
at com.sun.mail.imap.protocol.IMAPProtocol.status(IMA PProtocol.java:727)
at com.sun.mail.imap.IMAPFolder.getUIDValidity(IMAPFo lder.java:1722)
... 33 more

2008-04-16 15:31:10,559 INFO [btpool0-59] [name=jscalf@zt2.rutgers.edu;mid=14;ip=165.230.78.1 58;ua=ZimbraWebClient - FF2.
0 (Linux)/5.0.4_GA_2101.UBUNTU6;ds=ferna@andromeda;] SoapEngine - handler exception
com.zimbra.common.service.ServiceException: system failure: A14 NO [ALERT] STATUS failed
ExceptionId:btpool0-59:1208374270559:4945c3377364cbbf
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:253)
at com.zimbra.cs.datasource.ImapImport.importData(Ima pImport.java:369)
at com.zimbra.cs.datasource.DataSourceManager.importD ata(DataSourceManager.java:148)
at com.zimbra.cs.service.mail.ImportData.handle(Impor tData.java:62)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:391)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:250)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:156)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:266)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:177)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:487)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1093)
at org.mortbay.servlet.UserAgentFilter.doFilter(UserA gentFilter.java:81)
at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter .java:132)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:716)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.java:406)
at org.mortbay.jetty.handler.ContextHandlerCollection .handle(ContextHandlerCollection.java:211)
at org.mortbay.jetty.handler.HandlerCollection.handle (HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.handler.RewriteHandler.handle(Re writeHandler.java:176)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:506)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:442)
Caused by: javax.mail.MessagingException: A14 NO [ALERT] STATUS failed;
nested exception is:
com.sun.mail.iap.CommandFailedException: A14 NO [ALERT] STATUS failed
at com.sun.mail.imap.IMAPFolder.getUIDValidity(IMAPFo lder.java:1730)
at com.zimbra.cs.datasource.ImapImport.importData(Ima pImport.java:187)
... 32 more
Caused by: com.sun.mail.iap.CommandFailedException: A14 NO [ALERT] STATUS failed
at com.sun.mail.iap.Protocol.handleResult(Protocol.ja va:328)
at com.sun.mail.imap.protocol.IMAPProtocol.status(IMA PProtocol.java:727)
at com.sun.mail.imap.IMAPFolder.getUIDValidity(IMAPFo lder.java:1722)
... 33 more

[mmorse]

Might have been a folder naming issue, but reports currently working after upgrade to 5.0.5 (before more troubleshooting was done).

Anyone else hitting this error start by:
su - zimbra
zmprov aal user@domain.com zimbra.datasource debug

You should see a "Processing IMAP folder" message in /opt/zimbra/log/mailbox.log before the failure occurs that will tell you the name of the folder.

Try renaming the folder and see if that solves the problem. To rename the folder you can run:
zmmailbox -z -m user@domain.com rf {folder-path} {new-folder-path}
For example,
zmmailbox -z -m user@domain.com rf "/Test" "/Test1"

To turn off debug logging, you can run:
zmprov ral user@domain.com zimbra.datasource
Note: account logger setting will also go away if you restart the server.

If renaming the folder fixes the issue, please let us know the old folder name and we'll file a bug. If renaming the folder doesn't help, attach some mailbox.log snips with zimbra.datasource debugging enabled.