8.8.15 Patch 5 send-as error with attachment

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
pesaro.cesiuno
Posts: 1
Joined: Fri Dec 20, 2019 11:06 am

8.8.15 Patch 5 send-as error with attachment

Postby pesaro.cesiuno » Fri Dec 20, 2019 11:46 am

Hi everybody.
Since upgrade to latest patch users cannot send-as other user, via Persona setting, if attachment is present.
Account sender@xx.xx.xx has Persona set to send as account sender_as@xx.xx.xx
User is using webmail Ajax.
If email is sent without attachments there is no problem.
Error is:

method: [unknown]
msg: no such message: 212022
code: mail.NO_SUCH_MSG
detail: soap:Sender
trace: qtp366590980-31859:1576841412500:0e97fe18311986a5

This is from zimbra.soap log:

2019-12-20 12:21:49,399 DEBUG [qtp366590980-31275:https://xx.xx.xx/service/soap/SaveDraftRequest] [name=sender@xx.xx.xx;mid=171;ip=172.16.100.158;port=40642;ua=ZimbraWebClient - GC78 (Linux)/8.8.15_GA_3890;soapId=5185774c;] soap - Adding message body, incrementing size by 0 to 0.
2019-12-20 12:21:49,407 INFO [qtp366590980-31275:https://xx.xx.xx/service/soap/SaveDraftRequest] [name=sender@xx.xx.xx;mid=171;ip=172.16.100.158;port=40642;ua=ZimbraWebClient - GC78 (Linux)/8.8.15_GA_3890;soapId=5185774c;] mailop - Adding Message: id=212022, Message-ID=<1406965749.364100.1576840909399.JavaMail.zimbra@xx.xx.xx>, parentId=-1, folderId=6, folderName=Drafts acct=529d0f82-5760-41d8-88da-19697a29e847.
2019-12-20 12:21:49,422 INFO [qtp366590980-31275:https://xx.xx.xx/service/soap/SaveDraftRequest] [name=sender@xx.xx.xx;mid=171;ip=172.16.100.158;port=40642;ua=ZimbraWebClient - GC78 (Linux)/8.8.15_GA_3890;soapId=5185774c;] soap - SaveDraftRequest elapsed=24
2019-12-20 12:21:50,792 DEBUG [qtp366590980-32155:https://xx.xx.xx/service/soap/SaveDraftRequest] [name=sender@xx.xx.xx;mid=171;ip=172.16.100.158;port=40644;ua=ZimbraWebClient - GC78 (Linux)/8.8.15_GA_3890;soapId=5185774f;] soap - Adding message body, incrementing size by 0 to 0.
2019-12-20 12:21:50,805 INFO [qtp366590980-32155:https://xx.xx.xx/service/soap/SaveDraftRequest] [name=sender@xx.xx.xx;mid=171;ip=172.16.100.158;port=40644;ua=ZimbraWebClient - GC78 (Linux)/8.8.15_GA_3890;soapId=5185774f;] soap - SaveDraftRequest elapsed=14
2019-12-20 12:21:50,920 INFO [qtp366590980-32194:https://xx.xx.xx/service/upload?fmt=extended,raw] [name=sender@xx.xx.xx;mid=171;ip=172.16.100.158;port=40645;ua=Mozilla/5.0 (X11;; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36;] FileUploadServlet - Received plain: Upload: { accountId=529d0f82-5760-41d8-88da-19697a29e847, time=Fri Dec 20 12:21:50 CET 2019, size=57977, uploadId=79da5eae-9bef-43db-a0b0-2365b5e8dc57:2607fdac-a3d4-4327-a797-6f76e662bfa0, name=Calendario 2020 ferie collettive.pdf, path=/opt/zimbra/data/tmp/upload/upload_6245a321_16f19b64de2__8000_00006796.tmp }
2019-12-20 12:21:50,950 DEBUG [qtp366590980-32031:https://xx.xx.xx/service/soap/SaveDraftRequest] [name=sender@xx.xx.xx;mid=171;ip=172.16.100.158;port=40646;ua=ZimbraWebClient - GC78 (Linux)/8.8.15_GA_3890;soapId=51857750;] soap - Adding message body, incrementing size by 0 to 0.
2019-12-20 12:21:50,950 DEBUG [qtp366590980-32031:https://xx.xx.xx/service/soap/SaveDraftRequest] [name=sender@xx.xx.xx;mid=171;ip=172.16.100.158;port=40646;ua=ZimbraWebClient - GC78 (Linux)/8.8.15_GA_3890;soapId=51857750;] soap - Adding upload Calendario 2020 ferie collettive.pdf, incrementing size by 77109 to 77109.
2019-12-20 12:21:50,975 INFO [qtp366590980-32031:https://xx.xx.xx/service/soap/SaveDraftRequest] [name=sender@xx.xx.xx;mid=171;ip=172.16.100.158;port=40646;ua=ZimbraWebClient - GC78 (Linux)/8.8.15_GA_3890;soapId=51857750;] soap - SaveDraftRequest elapsed=26
2019-12-20 12:21:56,451 DEBUG [qtp366590980-31690:https://xx.xx.xx/service/soap/SendMsgRequest] [name=sender_as@xx.xx.xx;aname=sender@xx.xx.xx;mid=1254;ip=172.16.100.158;port=40657;ua=ZimbraWebClient - GC78 (Linux)/8.8.15_GA_3890;soapId=51857757;] soap - Adding message body, incrementing size by 0 to 0.
2019-12-20 12:21:56,452 WARN [qtp366590980-31690:https://xx.xx.xx/service/soap/SendMsgRequest] 2019-12-20 12:21:56,452 WARN [qtp366590980-31690:https://xx.xx.xx/service/soap/SendMsgRequest] [name=sender_as@xx.xx.xx;aname=sender@xx.xx.xx;mid=1254;ip=172.16.100.158;port=40657;ua=ZimbraWebClient - G
C78 (Linux)/8.8.15_GA_3890;soapId=51857757;] SoapEngine - handler exception
com.zimbra.cs.mailbox.MailServiceException$NoSuchItemException: no such message: 212022
ExceptionId:qtp366590980-31690:https://xx.xx.xx/service/soap/SendMsgRequest:1576840916452:0e97fe18311986a5
Code:mail.NO_SUCH_MSG Arg:(itemId, IID, "212022")
at com.zimbra.cs.mailbox.MailServiceException.NO_SUCH_MSG(MailServiceException.java:219)
at com.zimbra.cs.mailbox.MailItem.noSuchItem(MailItem.java:1761)
at com.zimbra.cs.db.DbMailItem.getBy(DbMailItem.java:2531)
at com.zimbra.cs.db.DbMailItem.getById(DbMailItem.java:2495)
at com.zimbra.cs.mailbox.MailItem.getById(MailItem.java:1680)
at com.zimbra.cs.mailbox.MailItem.getById(MailItem.java:1676)
at com.zimbra.cs.mailbox.Mailbox.getItemById(Mailbox.java:2982)
at com.zimbra.cs.mailbox.Mailbox.getItemById(Mailbox.java:2896)
at com.zimbra.cs.mailbox.Mailbox.getItemById(Mailbox.java:2887)
at com.zimbra.cs.mailbox.Mailbox.getMessageById(Mailbox.java:4552)
at com.zimbra.cs.service.mail.ParseMimeMessage.attachPart(ParseMimeMessage.java:848)
at com.zimbra.cs.service.mail.ParseMimeMessage.handleAttachments(ParseMimeMessage.java:495)
at com.zimbra.cs.service.mail.ParseMimeMessage.parseMimeMsgSoap(ParseMimeMessage.java:384)
at com.zimbra.cs.service.mail.ParseMimeMessage.parseMimeMsgSoap(ParseMimeMessage.java:206)
at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg.java:178)
at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg.java:107)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:667)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:512)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:283)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:308)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:217)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:214)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623)
at org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:214)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
at com.zimbra.cs.servlet.CsrfFilter.doFilter(CsrfFilter.java:164)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
at com.zimbra.cs.servlet.RequestStringFilter.doFilter(RequestStringFilter.java:54)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:59)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
at com.zimbra.cs.servlet.ETagHeaderFilter.doFilter(ETagHeaderFilter.java:47)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
at com.zimbra.cs.servlet.ContextPathBasedThreadPoolBalancerFilter.doFilter(ContextPathBasedThreadPoolBalancerFilter.java:107)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
at com.zimbra.cs.servlet.ZimbraQoSFilter.doFilter(ZimbraQoSFilter.java:125)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
at com.zimbra.cs.servlet.ZimbraInvalidLoginFilter.doFilter(ZimbraInvalidLoginFilter.java:117)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
at org.eclipse.jetty.servlets.DoSFilter.doFilterChain(DoSFilter.java:482)
at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:327)
at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:297)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:540)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1700)
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345)
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1667)
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:220)
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:152)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at org.eclipse.jetty.rewrite.handler.RewriteHandler.handle(RewriteHandler.java:335)
at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:753)
at org.eclipse.jetty.server.handler.DebugHandler.handle(DebugHandler.java:83)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at org.eclipse.jetty.server.Server.handle(Server.java:505)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:427)
at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:321)
at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:159)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)
at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)
at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:698)
at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:804)
at java.base/java.lang.Thread.run(Thread.java:830)
2019-12-20 12:21:56,453 INFO [qtp366590980-31690:https://xx.xx.xx/service/soap/SendMsgRequest] [name=sender_as@xx.xx.xx;aname=sender@xx.xx.xx;mid=1254;ip=172.16.100.158;port=40657;ua=ZimbraWebClient - GC78 (Linux)/8.8.15_GA_3890;soapId=51857757;] soap - SendMsgRequest elapsed=3

Any idea? :?


zimbrafox
Posts: 4
Joined: Thu Jan 02, 2020 11:09 am

Re: 8.8.15 Patch 5 send-as error with attachment

Postby zimbrafox » Tue Jan 07, 2020 9:22 am

Hi,

same problem with p5

I think this is the same Problem like in this thread:

http://forums.zimbra.org/viewtopic.php?f=13&t=67507
sbsupport
Posts: 1
Joined: Wed Jan 08, 2020 10:02 am

Re: 8.8.15 Patch 5 send-as error with attachment

Postby sbsupport » Wed Jan 08, 2020 10:07 am

Yeah, this is pretty ugly and is currently creating great waves within our company.
I am a paying customer and just opened a case with maximum priority to speed up fixing process.
If you are paying customer and read this, pleas also create a support request with maximum priority.
This will enforce Zimbra to speed up the solution process.
Thanks Chris

Return to “Administrators”

Who is online

Users browsing this forum: No registered users and 15 guests