Oleg wrote: > Hello > > I use kmail and dbmail-2.0.7 > > When I attach file with russian characters in file-name, I get such mime > header: > > Content-Type: application/msword; > name*=koi8-r''%F0%D2%C1%D7%C9%CC%C1%20%CB%C1%CE%C1%CC%C1%2019%2E09%2Edoc > Content-Transfer-Encoding: base64 > Content-Disposition: attachment; > filename*="koi8-r''%F0%D2%C1%D7%C9%CC%C1%20%CB%C1%CE%C1%CC%C1%2019%2E09%
I'm no expert when it comes to utf7 encoding, but these headers don't look valid at all. Did these headers come from a message stored in dbmail already, or straight from kmail? Especially the parameters in Content-Type and Content-Disposition don't look kosher: weird parameter names and missing chars at the end. > > and kmail "eat" all memory, when I try to read this message. Thunderbird > can't > read this mail at all. > > But when I send this file by Thunderbird, mime header of attachment is: > > Content-Type: application/octet-stream; > name="=?KOI8-R?Q?=F0=D2=C1=D7=C9=CC=C1_=CB=C1=CE=C1=CC=C1_19=2E09=2Edoc?=" > Content-Transfer-Encoding: base64 > Content-Disposition: attachment; > filename="=?KOI8-R?Q?=F0=D2=C1=D7=C9=CC=C1_=CB=C1=CE=C1=CC=C1_19=2E09=2Edoc?=" > > and I can read this mail by kmail and thunderbird. And now suddenly the headers look better. > > Why kmail put name*= in mime header of attach? And why I can't read such mail > by kmail? Indeed. I'd say you hit a kmail bug. It's utf7 encoding routines may be broken. Looks like stack corruptions to me. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl
