Zimbra not affected by log4j (CVE-2021-44228)
After intensive review and testing, Zimbra Development determined that the 0-day exploit vulnerability for log4j (CVE-2021-44228) does not affect the current Supported Zimbra versions (9.0.0 & 8.8.15). Zimbra Collaboration Server currently uses log4j1 version 1.2.16 which doesn't contain the lookup expression feature that is found within versions 2.0 to 2.17, which is the cause of the vulnerability. Also, Redhat (CVE-2021-4104) vulnerability does not affect the Zimbra Collaboration Server version (8.8.15 & 9.0.0). For this vulnerability to affect the server, it needs JMSAppender, which the ZCS Server does not use, and the ability to append configuration files.

Error on local folder email

If Zimbra Desktop had a sync failure, it may have told you to post your error in this section.
Posts: 1
Joined: Thu Dec 02, 2021 2:14 pm

Error on local folder email

Postby Dario955i » Thu Dec 02, 2021 2:22 pm

I hope this forum is still working. I was checking my local email saved in the local forder. Structure is correct and if I passover the folder it shows number and size of the stored email, but once I click on the specific folder I have this error (see below).

Any suggestion? I checked online but unfortunately without success.

method: [unknown]
msg: No such blob: mailbox=1, item=1148, change=1038
code: mail.NO_SUCH_BLOB
detail: soap:Sender
trace: com.zimbra.cs.mailbox.MailServiceException: No such blob: mailbox=1, item=1148, change=1038 ExceptionId:btpool0-131:1638454742548:caceee9a21dff446 Code:mail.NO_SUCH_BLOB at com.zimbra.cs.mailbox.MailServiceException.NO_SUCH_BLOB(MailServiceException.java:270) at com.zimbra.cs.mailbox.MailItem.getBlob(MailItem.java:971) at com.zimbra.cs.mailbox.MessageCache.fetchFromStore(MessageCache.java:230) at com.zimbra.cs.mailbox.MessageCache.getMimeMessage(MessageCache.java:166) at com.zimbra.cs.mailbox.Message.getMimeMessage(Message.java:428) at com.zimbra.cs.mailbox.Message.getMimeMessage(Message.java:409) at com.zimbra.cs.service.mail.ToXML.encodeMessageAsMP(ToXML.java:885) at com.zimbra.cs.service.mail.SearchResponse.add(SearchResponse.java:237) at com.zimbra.cs.service.mail.SearchResponse.add(SearchResponse.java:154) at com.zimbra.cs.service.mail.Search.putHits(Search.java:174) at com.zimbra.cs.service.mail.Search.handle(Search.java:123) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:412) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:287) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:158) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:303) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:206) at javax.servlet.http.HttpServlet.service(HttpServlet.java:814) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:218) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:422) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:585) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:988) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:415) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:429) at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
Body: {
SearchRequest: {
_jsns: "urn:zimbraMail",
fetch: 1,
html: 1,
limit: 100,
locale: {
_content: "it"
offset: 0,
query: "in:"inbox/2019"",
sortBy: "dateDesc",
types: "message",
tz: {
id: "Europe/Berlin"
Header: {
context: {
_jsns: "urn:zimbra",
account: {
_content: "local@host.local",
by: "name"
authToken: "(removed)",
notify: {
seq: 11
session: {
_content: 116,
id: 116
userAgent: {
name: "ZimbraWebClient - GC59 (Win)",
version: "7.3.1 GA"

User avatar
L. Mark Stone
Elite member
Elite member
Posts: 2309
Joined: Wed Oct 09, 2013 11:35 am
Location: Portland, Maine, US
ZCS/ZD Version: 8.8.15 Network Edition

Re: Error on local folder email

Postby L. Mark Stone » Thu Dec 02, 2021 2:36 pm

"No such blob" means the email blob on disk (typically in /opt/zimbra/store) is missing or unreadable.

Each email gets an entry in MariaDB, and the first few lines of each email's body are also stored in MariaDB, so when you look at the list of emails in the web client and see the first line or two of the email body, that's all being served from MariaDB. It's only after you click on an email listing to read the entire email that Zimbra endeavors to read the blob file from disk.

It does happen that the blobs on disk and MariaDB become incongruent, but only after a crash or hardware issue in my experience.

I'd start checking the infrastructure level first.

Hope that helps,
L. Mark Stone
Mission Critical Email - Zimbra VAR/BSP/Training Partner https://www.missioncriticalemail.com/
Zeta Alliance http://www.zetalliance.org/

Return to “Error Reports”

Who is online

Users browsing this forum: No registered users and 4 guests