Oleg wrote: > > But, may be write workaround in dbmail? > If dbmail can undestand name*= and filename*= syntax - it will be good !
Hahaha! Good joke! Sorry. But that's just such a bad idea for more than one reason. I mean, if it were outlook, I (have) might (to) consider, but kmail is open-source. No reason for the kmail community not to fix this. Au contraire! If kmail generates buggy headers, do other imap-server accomodate such a mess? I be damned if they do. Dbmail's own home-grown mime parser is a bitch to maintain, and for that reason alone it's deprecated. If you find a bug please do report and we can fix it together. But I'm not going to touch that code so we can accomodate bugs in other people's closets. Fixing kmail's utf7 code is probably easier to fix than creating a work-around in dbmail. Also, such a work-around is deprecated before it written: dbmail-2.2 will use none of the mime code you see in dbmail-2.0, so for dbmail-2.2 you'd have to write a totally new patch (against gmime, not dbmail). In short; a waste of time better spent reporting this bug to the kmail crowd. -- ________________________________________________________________ Paul Stevens mailto:[EMAIL PROTECTED] NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED] The Netherlands________________________________http://www.nfg.nl
