Mozilla Thunderbird (at least since version 1.5) and KMail encode non-ascii
attachment filename like this:
Content-Type: application/x-zip-compressed;
name*=ISO-8859-2''yk51x86_v851%20%B163.zip
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename*=ISO-8859-2''yk51x86_v851%20%B163.zip

OE can't understand it and so it gives the attachment a generic name
ATT#####.dat where ##### is some number. Is there any patch/kb
article/whatever to resolve the problem? Thanks in advance,
--
Regards,
Tomasz Grobelny

I'm not aware of any update for OE.

A couple of notes:

The reason you get the ATT##### is because of the * at the end of name*
and filename* keywords. OE is looking for them without the *. Not
finding a name it makes one up.

You get the .DAT when OE can't find the Content-Type: in the registry.
If the MIME type is properly registered, OE will create the correct file
extension. On my PC with your example, OE comes up with ATT####.ZIP for
the file name.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm


"Tomasz Grobelny" wrote in message
...
Mozilla Thunderbird (at least since version 1.5) and KMail encode
non-ascii
attachment filename like this:
Content-Type: application/x-zip-compressed;
name*=ISO-8859-2''yk51x86_v851%20%B163.zip
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename*=ISO-8859-2''yk51x86_v851%20%B163.zip

OE can't understand it and so it gives the attachment a generic name
ATT#####.dat where ##### is some number. Is there any patch/kb
article/whatever to resolve the problem? Thanks in advance,
--
Regards,
Tomasz Grobelny