[OGo-Users] Mozilla thunderbird and attachment filenames in ogo-webui

[Samuli Seppanen]

Hello everybody!

I recently stumbled across an annoying character encoding problem when 
using Mozilla Thunderbird in combination with OGo webmail. As always, 
the problem pops up when an attachment's filename contains scandivian 
characters (ä and ö, a.k.a. a and o umlauts). Long story short, here's 
how it goes:

Sending mail using Thunderbird (with default settings) and reading it 
with OGo webmail works just fine. All scandinavian characters (subject, 
text body) work just fine. If I attach an *.odt file with scandinavian 
characters in it to the composed message (in Thunderbird), OGo webmail 
shows the attachment name wrong.

* If I send the message with OGo webmail and read it from OGo webmail, 
all is well.
* If I send the message with Thunderbird and read it with Thunderbird 
all is ok.
* If I send the message with Evolution and read it with OGo webmail, 
there's the same problem as with Thunderbird

The file itself is created with OpenOffice 2.2 (Ubuntu Feisty Fawn 
7.04), and is UTF-8 encoded.

Here are the relevant part of the mail's source (sent with Thunderbird):

--- snip ---

User-Agent: Thunderbird 1.5.0.10 (X11/20070403)
MIME-Version: 1.0
To: Samuli Seppanen <samuli.seppanen@tietoteema.fi>
Subject: =?ISO-8859-1?Q?thunderbird-iso-=E4=F6=E5?=
Content-Type: multipart/mixed;
 boundary="------------020600050506060805000101"

This is a multi-part message in MIME format.
--------------020600050506060805000101
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

äöå

--------------020600050506060805000101
Content-Type: application/vnd.oasis.opendocument.text;
 name*=ISO-8859-1''%F6%E4%E5%2E%6F%64%74
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename*=ISO-8859-1''%F6%E4%E5%2E%6F%64%74

--- snip ---


The

filename*=ISO-8859-1''%F6%E4%E5%2E%6F%64%74

is the problem: it looks like that in OGo webmail, although it should be 
"äöå.odt". So can anybody tell if this is normal, and if there's a 
solution for this? Of course there's no way to avoid all character 
encoding problems, but it would be nice if the best / most used email 
clients would work seamlessly with OGo webmail.

Best regards,

Samuli Seppänen