I have Carbonio installed and updated to 23.6.0 and decided to install Carbonio Mail App in my Androind smartphone to give it a try... All work great except for this little tiny detail: it doesn't send any messages.
I kept looking into mailbox.log to see what was going on and found this message:
"com.zimbra.common.service.ServiceException: invalid request: missing required attribute: a"
You can see more debug below:
2023-06-26 21:08:02,336 WARN [qtp502800944-187: https://carbonio.myserver/service/soap/SendMsgRequest ] [name=cliente11@carbonio.mydom;mid=4;ip=192.168.10.144;oip=XXX, 192.168.10.1;oproto=https;port=57832;ua=Mail - Android - v1.2.4_release - API28 - moto e6s;soapId=5d2540c5;] SoapEngine - handler exception com.zimbra.common.service.ServiceException: invalid request: missing required attribute: a ExceptionId:qtp502800944-187: https://carbonio.myserver/service/soap/SendMsgRequest:1687824482336:53abf7ae719c9304 Code:service.INVALID_REQUEST at com.zimbra.common.service.ServiceException.INVALID_REQUEST(ServiceException.java:293) at com.zimbra.common.soap.Element.checkNull(Element.java:401) at com.zimbra.common.soap.Element.getAttribute(Element.java:336) at com.zimbra.cs.service.mail.ParseMimeMessage$MessageAddresses.add(ParseMimeMessage.java:1124) at com.zimbra.cs.service.mail.ParseMimeMessage.parseMimeMsgSoap(ParseMimeMessage.java:322) at com.zimbra.cs.service.mail.ParseMimeMessage.parseMimeMsgSoap(ParseMimeMessage.java:140) at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg.java:209) at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg.java:100) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:684) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:508) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:278) at com.zimbra.soap.SoapServlet.doWork(SoapServlet.java:310) at com.zimbra.soap.SoapServlet.doPost(SoapServlet.java:219) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at com.zimbra.cs.servlet.ZimbraServlet.service(ZimbraServlet.java:208) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:799) at org.eclipse.jetty.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1656) at org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:292) at org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193) at org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1626) at com.zimbra.cs.servlet.CsrfFilter.doFilter(CsrfFilter.java:152) at org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:193)
So... what is this attribute "a" that is missing?
The developers of the mobile application broke sending in Carbonio Mail version 1.2.2. In this version, we added a section in the settings for specifying the sender's address and selecting the departure address. Apparently, in the full version of Carbonio, this works fine, since there is no limit on sending from one account. But in Carbonio CE, sending broke. Since then, versions 1.2.3 and 1.2.4 have been released, but no one is in a hurry to fix it. These topics are also only accessed by the unfortunate voluntary testers of the CE version.
The solution to the issue is simple. Find and install APK Carbonio Mail 1.2.0. Searching the Internet, I found and installed this version. Mail is sent. Don't forget to disable auto-update.
MAX.... first of all tyvm for your answer... I was quite frustrated for the silence on this topic.
At the same time I'm happy to know there is a possible solution to it I'm also very concerned now: "no one is in a hurry to fix it" + "unfortunate voluntary testers of the CE version"
Those are very very terrifying statements to see in here. AFAIK Community stands by be active and be stimulated by Software Development, not only because it's fun but also because it's the way to make development process more effective. More people testing, more bug reports, more fixing, more stable product at the end. All of that to be done ASAP and not "not in a hurry" way.
I wish we can improve communication, get faster answers in this Forum and bring more testers over here to share experiences and learn how to fix those minor issues so we have a more stable and reliable Carbonio CE.
I'll test your suggestion and give you a feedback ASAP.
Regards
You nailed it MAX... tyvm.
I did test Carbonio APP 1.2.0 and it's working as expected =)
Awesome!
To help others I'm leaving here the link from where I download it - Carbonio Mail App V 1.2.0
Hope a new and fixed version of Carbonio Mail APP get released on Google and Apple stores ASAP.
Once again, tyvm for your answer.
Regards
@anahuac, thanks for URL! It help other users.
The community on this forum is small and not very active. I am very glad that you are on this forum. And the more of those who not only write to the developers: "Fix it, it doesn't work", but independently look for ways to solve problems - the more active the forum will be!
The problem is still present in Android version 1.2.5. You can not upgrade from version 1.2.0! For outgoing mail to work properly, stay on version 1.2.0.
Dear developers, since version 1.2.2 the application does not send mail - it is inoperative and unusable!
P.S. Dear administration, remove the "Solved" icon from the topic - this is misleading forum participants. The problem is not solved. The current "solution" is not a solution, but a workaround. There can be only one solution - acknowledging the problem and publishing a link to the latest working version of the application - 1.2.1 for download from the official site.
@arman now it's working, congrats! only the notifications that in my case still didn't work.
Great news, @arman ! Application 1.2.6 sends mail! The choice of sender parameters is correct! We thank the developers for fixing this bug that has been preventing us from using the application for many months! Now the topic can be marked as solved! This is the best news today!
Application 1.2.6 sends mail! The choice of sender parameters is correct! We thank the developers for fixing this bug that has been preventing us from using the application for many months! Now the topic can be marked as solved! This is the best news today!