> > 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.
Yes, this headers come from kmail. > > 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. But, may be write workaround in dbmail? If dbmail can undestand name*= and filename*= syntax - it will be good ! __ Oleg
