Hi! Am 18.01.06 09:44 schrieb(en) Mişu Moldovan:
I've recently received a couple of messages with unknown encoding in headers that look like this:
[snip broken headers]
Granted, the sender used a broken MUA (PMMail 2000 Professional 2.20.2717),
Indeed!
but Balsa should have tried it's best to decode the above gibberish, it even has a special setting instructing it to use a user-defined encoding when none is specified. For now, this is used when encountering 8-bit characters in body and there is no encoding specified in the headers. Shouldn't this be extended to non-ASCII characters in headers without a specified encoding, like the above example?
Hmmm, I think this is a good idea, although I don't know at first glance if it is *simply* possible - the headers are processed by GMime which expects them to follow the standards...
On related notes I've recently tried the latest Sylpheed and Sylpheed Claws mail clients and I have some ideas that apply to Balsa also. Are you interested in hearing them?
Sure! Any hint for improvement is welcome!
Cheers, Albrecht.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Albrecht Dreß - Johanna-Kirchner-Straße 13 - D-53123 Bonn (Germany)
Phone (+49) 228 6199571 - mailto:albrecht dress arcor de
GnuPG public key: http://www.mynetcologne.de/~nc-dreszal/pubkey.asc
_________________________________________________________________________
Attachment:
pgpYmoNpZUqBC.pgp
Description: PGP signature