[dev] MIME Encoding and RFC 2231

[Jan Schneider]

Zitat von Michael M Slusarz <slusarz at bigworm.colorado.edu>:

> Quoting Michael M Slusarz <slusarz at bigworm.colorado.edu>:
>
>> http://www.faqs.org/rfcs/rfc2231.html
>
> Found this thread:
> https://mail.kde.org/pipermail/kdepim-users/2004-February/000299.html

That helped understanding the issue a lot.

> A viable idea would be to implement encoding the way that it appears 
> mutt gets
> around this problem - by sending both the invalid, RFC 2047 encoded 
> header and
> the RFC 2231 header.

Hm, maybe I've misread it, but didn't someone say in this thread that mutt
is *always* sending RFC 2231 headers? Or is this what you are talking
about? How can you send headers in both formats?

> And I think the "holier than thou attitude" shown by the developer in that
> thread is pretty repulsive.  I understand the need to follow standards, but
> turning your back on the way the rest of the world operates doesn't 
> seem to be
> a valid response.  You think Outlook sucks?  That's your opinion, but that
> doesn't mean you can just ignore it.

Exactly. I think we should in any case support decoding this format for
cases where the server doesn't do it on the fly. And if we have to use
*one* of these formats, it would be cool if we could let the user decide.
Making it a preference that can be turned on if most correspondents use
broken mail clients.
It could be done even fancier with formatting depending on the recipients,
storing their preferred format in Turba and automatically detecting and
storing their user clients in Turba when reading mail. Well, that might be
a bit overhead. :-)

Jan.

--
http://www.horde.org - The Horde Project
http://www.ammma.de - Neue Wege des Lernens
http://www.tip4all.de - Deine private Tippgemeinschaft