when sending an attachment using sqwebmail, lots of the time in Outlook, the attachment will show up as ATTXXXXXX.dat, and in kmail (my client of choice) will simply show up as 'unnamed'

Upon further investigation, I discovered that sqwebmail was generating MIME headers for the attachment MIME part like so: Content-Disposition: attachment; filename*0*=utf-8'en-us'test%202.zip Content-Type: application/zip; name*0*=iso-8859-1''test%202.zip Content-Transfer-Encoding: base64

When sending the same email using kmail, the MIME headers are generated as so: Content-Type: application/x-zip; name="test 2.zip" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="test 2.zip"

notice how the headers sqwebmail is generating have 'name*0*=' instead of just 'name=' ... and I think this is where the problem lies.

If I attach a file that doesn't have a space in the filename, it works fine, and doesn't include the *0*....

I don't know very much about mime, but this just doesn't seem right to me. Is it sqwebmail breaking the message, or kmail and outlook choking on it?

Thanks!

-Jeremy