Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
Go Back   Zimbra :: Forums > Zimbra Collaboration Suite > Mobility > Zimbra Mobile
Reload this Page Google Android and Zimbra

Welcome to the Zimbra :: Forums!
Welcome, if you would like to post a comment please register. We also encourage you to explore all things Zimbra with our team and members of the community.

Reply
Page 6 of 11 « First < 45 6 78
 
LinkBack Thread Tools Search this Thread Display Modes
  #51 (permalink)  
Old 02-12-2010, 06:57 AM
Moderator
  
Posts: 7,929
Default
No need for sarcasm when the issue is quiet obviously with HTC. Why not point them to RFC 2045 (rfc2045) - Multipurpose Internet Mail Extensions (MIME) Part One and ask why they are not compliant with it

And on a final point we all know how Microsoft adheres to standards; probably why they let the HTC connect
__________________
Reply With Quote
  #52 (permalink)  
Old 02-12-2010, 07:11 AM
Junior Member
  
Posts: 7
Default Point proven
No reason for sarcasm?

ZIMBRA:
Quote:
Originally Posted by uxbod View Post
... the issue is quiet obviously with HTC ...
HTC:
"... the issue is quiet obviously with ZIMBRA ..."
Reply With Quote
  #53 (permalink)  
Old 02-12-2010, 07:19 AM
Moderator
  
Posts: 7,929
Default
Read the RFC it clearly shows how charset should be set and how HTC should be implementing it. At the end of the day one product is being RFC compliant the other isn't.
__________________
Reply With Quote
  #54 (permalink)  
Old 02-12-2010, 09:17 AM
Zimbra Consultant & Moderator
  
Posts: 20,317
Default
Quote:
Originally Posted by ingo View Post
Great idea! So I just write a mail to Bill Gates and my ZIMBRA/HTC Android issues will get fixed.

<sarcasm>Why did I ever wasted my time on this forum?</sarcasm>
No sarcastic comments on the forums please, do not do it again.

Perhaps if Microsoft followed standards then HTC might decide to release a fix for their problem. As I've already said, the fact Exchange accepts an badly formed message is no reason for Zimbra to also produce a non-standard mail server. Please read the bug report for details of why it's an HTC problem.
__________________
Regards


Bill
Reply With Quote
  #55 (permalink)  
Old 03-04-2010, 01:59 AM
Active Member
  
Posts: 31
Default
Quote:
Originally Posted by phoenix View Post
No sarcastic comments on the forums please, do not do it again.

Perhaps if Microsoft followed standards then HTC might decide to release a fix for their problem. As I've already said, the fact Exchange accepts an badly formed message is no reason for Zimbra to also produce a non-standard mail server. Please read the bug report for details of why it's an HTC problem.
I have a same problem on HTC Tatoo.

Code:
Message-ID: <1B2547E6-9CBF-45F6-BB18-CCA673AA3A1C@mondomaine.fr>
To: antony@test.fr
Subject: Hh
Importance: Normal
MIME-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_Part_1_1267692574849"

------=_Part_1_1267692574849
Content-Type: text/plain;
        charset= utf-8
Content-Transfer-Encoding: utf-8
Content-Disposition: inline


Cc

Envoy?? depuis mon HTC

------=_Part_1_1267692574849
Content-Type: text/html;
        charset= utf-8
Content-Transfer-Encoding: utf-8
Content-Disposition: inline


Cc<br><br>Envoy?? depuis mon HTC

------=_Part_1_1267692574849--


2010-03-04 09:49:41,771 WARN  [btpool0-37://192.168.1.223:80/Microsoft-Server-ActiveSync?Cmd=SendMail&SaveInSent=T&User=antony.martineau@mondomaine.fr&DeviceId=HTCAnd28305ced&DeviceType=htctattoo] [name=antony.martineau@mondomaine.fr;mid=47;ip=192.168.30.17;Cmd=SendMail;DeviceID=HTCAnd28305ced;] sync - Exception while processing message as meeting invitation
java.io.IOException: Unknown encoding: utf-8
        at javax.mail.internet.MimePartDataSource.getInputStream(MimePartDataSource.java:108)
        at com.sun.mail.handlers.text_plain.getContent(text_plain.java:90)
        at javax.activation.DataSourceDataContentHandler.getContent(DataHandler.java:775)
        at javax.activation.DataHandler.getContent(DataHandler.java:522)
        at javax.mail.internet.MimeBodyPart.getContent(MimeBodyPart.java:630)
        at com.zimbra.zimbrasync.commands.SendMail.processAsMeetingMessage(SendMail.java:247)
        at com.zimbra.zimbrasync.commands.SendMail.sendMail(SendMail.java:112)
        at com.zimbra.zimbrasync.ZimbraSyncServlet.processPostRequest(ZimbraSyncServlet.java:370)
        at com.zimbra.zimbrasync.ZimbraSyncServlet.doPost(ZimbraSyncServlet.java:275)
        at com.zimbra.zimbrasync.ZimbraSync$HttpHandler.doPost(ZimbraSync.java:33)
        at com.zimbra.cs.extension.ExtensionDispatcherServlet.service(ExtensionDispatcherServlet.java:99)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
        at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
        at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
        at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:155)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        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:418)
        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.handler.DebugHandler.handle(DebugHandler.java:77)
        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:543)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:939)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
2010-03-04 09:49:41,925 WARN  [btpool0-37://192.168.1.223:80/Microsoft-Server-ActiveSync?Cmd=SendMail&SaveInSent=T&User=antony.martineau@mondomaine.fr&DeviceId=HTCAnd28305ced&DeviceType=htctattoo] [name=antony.martineau@mondomaine.fr;mid=47;ip=192.168.30.17;Cmd=SendMail;DeviceID=HTCAnd28305ced;] sync - Mailbox access exception
com.zimbra.common.service.ServiceException: system failure: Unable to send message
ExceptionId:btpool0-37://192.168.1.223:80/Microsoft-Server-ActiveSync?Cmd=SendMail&SaveInSent=T&User=antony.martineau@mondomaine.fr&DeviceId=HTCAnd28305ced&DeviceType=htctattoo:1267692581925:e0f3d003104ca276
Code:service.FAILURE
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:248)
        at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:492)
        at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:308)
        at com.zimbra.zimbrasync.commands.SendMail.sendMail(SendMail.java:189)
        at com.zimbra.zimbrasync.commands.SendMail.sendMail(SendMail.java:182)
        at com.zimbra.zimbrasync.commands.SendMail.sendMail(SendMail.java:118)
        at com.zimbra.zimbrasync.ZimbraSyncServlet.processPostRequest(ZimbraSyncServlet.java:370)
        at com.zimbra.zimbrasync.ZimbraSyncServlet.doPost(ZimbraSyncServlet.java:275)
        at com.zimbra.zimbrasync.ZimbraSync$HttpHandler.doPost(ZimbraSync.java:33)
        at com.zimbra.cs.extension.ExtensionDispatcherServlet.service(ExtensionDispatcherServlet.java:99)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
        at com.zimbra.cs.servlet.SetHeaderFilter.doFilter(SetHeaderFilter.java:79)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
        at org.mortbay.servlet.UserAgentFilter.doFilter(UserAgentFilter.java:81)
        at org.mortbay.servlet.GzipFilter.doFilter(GzipFilter.java:155)
        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
        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:418)
        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.handler.DebugHandler.handle(DebugHandler.java:77)
        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:543)
        at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:939)
        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:755)
        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
        at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
        at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
Caused by: com.zimbra.cs.mailbox.MailSender$SafeMessagingException: IOException while sending message; chained exception is:
        java.io.IOException: javax.mail.MessagingException: Unknown encoding: utf-8
        at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:779)
        at com.zimbra.cs.mailbox.MailSender.sendMessageToHost(MailSender.java:752)
        at com.zimbra.cs.mailbox.MailSender.sendMessage(MailSender.java:672)
        at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(MailSender.java:415)
        ... 36 more
2010-03-04 09:49:41,925 INFO  [btpool0-37://192.168.1.223:80/Microsoft-Server-ActiveSync?Cmd=SendMail&SaveInSent=T&User=antony.martineau@mondomaine.fr&DeviceId=HTCAnd28305ced&DeviceType=htctattoo] [name=antony.martineau@mondomaine.fr;mid=47;ip=192.168.30.17;Cmd=SendMail;DeviceID=HTCAnd28305ced;] sync - HTTP/1.1 500 Mailbox access error
no issue??
Reply With Quote
  #56 (permalink)  
Old 03-04-2010, 02:21 AM
Moderator
  
Posts: 7,929
Default
Its the same thing; not RFC compliant.
__________________
Reply With Quote
  #57 (permalink)  
Old 03-04-2010, 02:23 AM
Active Member
  
Posts: 31
Default
So, there is no solution?
The only solution is that HTC implement a good UTF-8 encoding method ?
Reply With Quote
  #58 (permalink)  
Old 03-04-2010, 02:27 AM
Moderator
  
Posts: 7,929
Default
No; they use a encoding method that is supported as per the RFC.
__________________
Reply With Quote
  #59 (permalink)  
Old 03-04-2010, 02:36 AM
Active Member
  
Posts: 31
Default
A new firmware or update of htc tatoo can resolve the problem?
Reply With Quote
  #60 (permalink)  
Old 03-04-2010, 02:37 AM
Moderator
  
Posts: 7,929
Default
No idea sorry ... you would need to raise the question with HTC as this is not a Zimbra issue.
__________________
Reply With Quote
Reply
Page 6 of 11 « First < 45 6 78

« Previous Thread | Today's Posts or Week's Posts | Next Thread »

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode


Similar Threads

Product Information

Why Join?

Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.

blog.zimbra.com


Home - Blog - Contact Us - Archive - Top


 

SEO by vBSEO ©2011, Crawlability, Inc.