Printing email problem

[stock99]

Hi,

For some reason when user print 'certain email'(not all have problem) from web-client (firefox 2.0.13 or 3beta5 ) , the email body will be some unreadable character but email address, subject and other info on the top of page is readable. We are using xerox workstation 4.5 . Has anyone encounter this?

ps: zimbra version 5.0.0 (run in RHEL5).

[ArcaneMagus]

Does print preview display the same odd characters? It sounds like the encoding scheme used on the email is not converting properly to whatever your printer can accept.

[Mike Scholes]

Two of us getting the same here on 5.0.6

[jmarriott]

Greetings,

Did this problem get fixed for anyone? We've just upgraded to Zimbra 5 and have started experiencing the same sort of problem.

Thanks,
Jon

[Mike Scholes]

After we installed FF3 final release it prints fine.

[jmarriott]

Hi Mike,

That fixed one of my users up too. The other one still has to print via a copy and paste into Writer - an elegant workaround if ever there was one!

Thanks for responding,
Jon

[mmorse]

Is it this issue? Bad print output from ajax client

[jmarriott]

Yes, it looks like it is, thanks.

I used Firebug, as suggested in the bug report, to change the style tag in the span that contains the body text and it printed ok.

Could you let me know what file I must alter on the Zimbra server so that everyone gets this change? I've tried a bit of grepping through /opt/zimbra/jetty but nothing is obviously relevant...

Thanks,
Jon

[jholder]

Yes, it looks like it is, thanks.

I used Firebug, as suggested in the bug report, to change the style tag in the span that contains the body text and it printed ok.

Could you let me know what file I must alter on the Zimbra server so that everyone gets this change? I've tried a bit of grepping through /opt/zimbra/jetty but nothing is obviously relevant...

Thanks,
Jon

We think this is a firefox issue, and not a Zimbra server issue. A firefox update should be out that will fix it.

[jmarriott]

We think this is a firefox issue, and not a Zimbra server issue. A firefox update should be out that will fix it.

I agree, it sounds like an FF issue. That said, if I can solve the problem for all my users in 30 seconds by altering a single file in Zimbra's tree then I'd like to do that rather than the infinitely more painful alternative.