Zimbra offers Open Source email server software and shared calendar for Linux and the Mac
 
Go Back   Zimbra - Forums > Zimbra Collaboration Suite > Administrators

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
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 02-22-2007, 09:34 AM
Intermediate Member
 
Posts: 22
Angry Unreadable message without charset

Some mails happen to have no default charset ( Content-Type: text/plain; charset) and as result it cannot be read by Zimbra.

Most of the mails are sent as UTF-8 and some as ISO-8859-7 with exception those without charset . . .

Can i change the default charset on Zimbra ???

A noticed that not even the xxx.msg file on storage is readable . . .

Ubuntu 6.10 Server
Zimbra Open Source Edition 4.5.2

Any help will be deeply appreciated
Reply With Quote
  #2 (permalink)  
Old 02-22-2007, 11:34 AM
Zimbra Employee
 
Posts: 1,434
Default Bug 13058

There's an enahancement request for this (bug 13058) in bugzilla. Please vote for it!

You might be able to work around this by setting Java's default charset appropriately. I'm not sure how that's done, however. Perhaps setting the LC_CTYPE UNIX environment variable, or adding -Dfile.encoding=iso-8859-7 to tomcat's command line.

And it's always a good idea to get your correspondents to stop using broken mailers!
__________________
Bugzilla - Wiki - Downloads - Before posting... Search!
Reply With Quote
  #3 (permalink)  
Old 02-23-2007, 01:53 AM
Intermediate Member
 
Posts: 22
Default

Thanx a lot!!

Found this :
export LANG="el_GR.UTF-8"
or

apt-get install localeconf
dpkg-reconfigure localeconf

https://help.ubuntu.com/community/LocaleConf
Reply With Quote
  #4 (permalink)  
Old 02-23-2007, 04:32 AM
Intermediate Member
 
Posts: 22
Default

Some update:

Some HTML messages are sent with subject in UTF-8 but with body in iso-8859-7,
the subject is readble but not the body. If specify to read everything as text the are all readable . . .

Finally found out that amavisd-new was messing up with the message headers, as all messages that was unreadable fwere found at /quarantine and amavisd-new had add an extra header : BAD HEADER non-encoded 8bit

Now trying a workaround for this . .

Last edited by RaNd : 02-23-2007 at 07:32 AM.
Reply With Quote
Reply


Thread Tools
Display Modes


Similar Threads

Why Join?

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

Zimbrablog.com




 

Search Engine Optimization by vBSEO 3.1.0