[SOLVED] Attachments with 0 bits in webmail (ok in Outlook)

[georgelazar]

Hi,

I have a strange issue, at one user the attachments from a part of the messages have 0 bits on webmail interface but downloaded with Outlook the attachments can be seen/accessed. The senders are various, others in CC or TO field can see the attachments in both webmail and Outlook (2007). The attachments can be .jpg, .xls, .html, etc.. no pattern.
It doesn't matter the browser (IE 8 and FF 3.5), Windows version (tried XP Pro and Vista Business).
Also tried AJAX and HTML interface on webmail, tried another theme and default one, the same thing.
I'm running Zimbra 6.0.4 on Ubuntu 8.04 64bit.

No space issues on the hdd, all services are running..
Also the user receive messages with attachments from various senders and attachments can bee seen/downloaded from webmail. The COS doesn't have Disable attachments view checked.

When I try to forward the message from webmail if I don't uncheck the attachments (which have 0 bit) I can't send the message, the following error found in mailbox.log:

####
2010-02-18 12:59:11,807 INFO [btpool0-1687://webmail.example.com/service/soap/SendMsgRequest] [name=name@example.com;mid=27;ip=192.168.5.151;ua=Z imbraWebClient - IE7 (Win)/6.0.4_GA_2038.UBUNTU8_64;] soap - SendMsgRequest
2010-02-18 12:59:11,826 WARN [MimeMessageThread] [] misc - Unable to write MimeMessage to output stream.
java.io.FileNotFoundException: /opt/zimbra/data/tmp/expand2031298827987779393.tnef (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.jav a:106)
at net.freeutils.tnef.RawInputStream.<init>(RawInputS tream.java:160)
at net.freeutils.tnef.RawInputStream.<init>(RawInputS tream.java:143)
at net.freeutils.tnef.mime.RawDataSource.getInputStre am(RawDataSource.java:76)
at com.zimbra.common.mime.DataSourceWrapper.getInputS tream(DataSourceWrapper.java:60)
at javax.activation.DataHandler.writeTo(DataHandler.j ava:290)
at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyP art.java:1381)
at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyP art.java:852)
at javax.mail.internet.MimeMultipart.writeTo(MimeMult ipart.java:452)
at com.sun.mail.handlers.multipart_mixed.writeTo(mult ipart_mixed.java:98)
at javax.activation.ObjectDataContentHandler.writeTo( DataHandler.java:869)
at javax.activation.DataHandler.writeTo(DataHandler.j ava:302)
at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyP art.java:1381)
at javax.mail.internet.MimeMessage.writeTo(MimeMessag e.java:1742)
at javax.mail.internet.MimeMessage.writeTo(MimeMessag e.java:1718)
at com.zimbra.cs.mime.MimeMessageOutputThread.run(Mim eMessageOutputThread.java:52)
at java.lang.Thread.run(Thread.java:619)
2010-02-18 12:59:11,837 WARN [MimeMessageThread] [] misc - Unable to write MimeMessage to output stream.
java.io.FileNotFoundException: /opt/zimbra/data/tmp/expand2031298827987779393.tnef (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.jav a:106)
at net.freeutils.tnef.RawInputStream.<init>(RawInputS tream.java:160)
at net.freeutils.tnef.RawInputStream.<init>(RawInputS tream.java:143)
at net.freeutils.tnef.mime.RawDataSource.getInputStre am(RawDataSource.java:76)
at com.zimbra.common.mime.DataSourceWrapper.getInputS tream(DataSourceWrapper.java:60)
at javax.activation.DataHandler.writeTo(DataHandler.j ava:290)
at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyP art.java:1381)
at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyP art.java:852)
at javax.mail.internet.MimeMultipart.writeTo(MimeMult ipart.java:452)
at com.sun.mail.handlers.multipart_mixed.writeTo(mult ipart_mixed.java:98)
at javax.activation.ObjectDataContentHandler.writeTo( DataHandler.java:869)
at javax.activation.DataHandler.writeTo(DataHandler.j ava:302)
at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyP art.java:1381)
at javax.mail.internet.MimeMessage.writeTo(MimeMessag e.java:1742)
at javax.mail.internet.MimeMessage.writeTo(MimeMessag e.java:1718)
at com.zimbra.cs.mime.MimeMessageOutputThread.run(Mim eMessageOutputThread.java:52)
at java.lang.Thread.run(Thread.java:619)
2010-02-18 12:59:11,897 INFO [btpool0-1687://webmail.example.com/service/soap/SendMsgRequest] [name=name@example.com;mid=27;ip=192.168.5.151;ua=Z imbraWebClient - IE7 (Win)/6.0.4_GA_2038.UBUNTU8_64;] mailop - Adding Message: id=26873, Message-ID=<601374719.8060.1266490751812.JavaMail.root@mx1 >, parentId=26866, folderId=5, folderName=Sent.
2010-02-18 12:59:11,909 INFO [btpool0-1687://webmail.example.com/service/soap/SendMsgRequest] [name=name@example.com;mid=27;ip=192.168.5.151;ua=Z imbraWebClient - IE7 (Win)/6.0.4_GA_2038.UBUNTU8_64;] smtp - Sending message to MTA at localhost, port 25: Message-ID=<601374719.8060.1266490751812.JavaMail.root@mx1 >, origMsgId=8790fee3-22de-4481-83f4-7c97c4e8e4f5:26583, replyType=w
2010-02-18 12:59:11,919 INFO [btpool0-1687://webmail.example.com/service/soap/SendMsgRequest] [name=name@example.com;mid=27;ip=192.168.5.151;ua=Z imbraWebClient - IE7 (Win)/6.0.4_GA_2038.UBUNTU8_64;] mailop - Deleting Message (id=26873).
2010-02-18 12:59:11,955 INFO [btpool0-1687://webmail.example.com/service/soap/SendMsgRequest] [name=name@example.com;mid=27;ip=192.168.5.151;ua=Z imbraWebClient - IE7 (Win)/6.0.4_GA_2038.UBUNTU8_64;] SoapEngine - handler exception
com.zimbra.common.service.ServiceException: system failure: Unable to send message
ExceptionId:btpool0-1687://webmail.example.com/service/soap/SendMsgRequest:1266490751955:28f097aecf19ffe0
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:247)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:453)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:280)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:237)
at com.zimbra.cs.service.mail.SendMsg.doSendMessage(S endMsg.java:190)
at com.zimbra.cs.service.mail.SendMsg.handle(SendMsg. java:150)
at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng ine.java:418)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:272)
at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:156)
at com.zimbra.soap.SoapServlet.doWork(SoapServlet.jav a:291)
at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:212)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:727)
at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra Servlet.java:181)
at javax.servlet.http.HttpServlet.service(HttpServlet .java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(Ser vletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedCha in.doFilter(ServletHandler.java:1166)
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:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(Se rvletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle( SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(Se ssionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(Co ntextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebA ppContext.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(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.rewrite.RewriteHandler.h andle(RewriteHandler.java:230)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.handler.DebugHandler.handle(Debu gHandler.java:77)
at org.mortbay.jetty.handler.HandlerWrapper.handle(Ha ndlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(Htt pConnection.java:543)
at org.mortbay.jetty.HttpConnection$RequestHandler.co ntent(HttpConnection.java:939)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser. java:755)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpPa rser.java:212)
at org.mortbay.jetty.HttpConnection.handle(HttpConnec tion.java:405)
at org.mortbay.io.nio.SelectChannelEndPoint.run(Selec tChannelEndPoint.java:409)
at org.mortbay.thread.BoundedThreadPool$PoolThread.ru n(BoundedThreadPool.java:451)
Caused by: com.zimbra.cs.mailbox.MailSender$SafeMessagingExce ption: IOException while sending message; chained exception is:
java.io.FileNotFoundException: /opt/zimbra/data/tmp/expand2031298827987779393.tnef (No such file or directory)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTr ansport.java:779)
at javax.mail.Transport.send0(Transport.java:191)
at javax.mail.Transport.send(Transport.java:142)
at com.zimbra.cs.mailbox.MailSender.sendMessage(MailS ender.java:612)
at com.zimbra.cs.mailbox.MailSender.sendMimeMessage(M ailSender.java:376)
... 37 more

####

I have repleced the user and domain name.

Please advise,
Thanks!

[liverpoolfcfan]

Check your "Class Of Service" (COS) and the COS of the people who can see the attachments.

In the Domain Administration GUI - Within COS - on the "Advanced" tab - there is an option

Disable attachment viewing from web mail UI [ ]

Perhaps your COS has this checked and the other peoples don't ?

[georgelazar]

All the COS used have that option inactive, also that account doesn't have it enabled in particular. That was the first thing that I have checked, but the bizzare issue is that not all the attachments have 0 bits (all the attachments from the same message, yes) but there are old and new messages with correct size that can be downloaded..

[georgelazar]

The error in the log is:
java.io.FileNotFoundException: /opt/zimbra/data/tmp/expand2031298827987779393.tnef (No such file or directory)

I assume that zimbra store the attachment in that temporary file and when I try to forward the message with attachments (0 bit attachments) it fails with that error in the log. There is a lot of space available on that partition, so no problem here.
If I uncheck the attachments before forwarding the message then I can send it.

[Rich Graves]

Bug handling TNEF files was introduced in 6.0 (maybe also a late 5.x?) and fixed in 6.0.5. But you probably won't want to upgrade to 6.0.5 because it introduces reminders for shared calendars, to be corrected in 6.0.6.

This forum and bugzilla have some workarounds and a reference to Microsoft's own 10-year-old recommendation that Exchange server administrators turn off the nonstandard TNEF encoding for Internet mail.

[georgelazar]

Hi Rich,

Do you recommend waiting for 6.0.6 release and then upgrade?

Thanks!

[georgelazar]

Hi Rich,

I found the bug as fixed in 6.0.5, as you said. Most likelly I will wait for 6.0.6 then upgrade.
Thanks a lot for help.

George