![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Kari Hurtta wrote:
http://www.ietf.org/internet-drafts/draft-hurtta-eai-messagestore-00.txt
| To discover message is UTF8SMTP message may require that | all message header fields (including header fields from | MIME body parts) are parsed.
As always that violates anything I think to know about data abstraction and modularization. MIME part headers are not the business of agents transporting MIME 1.0 messages. You are not designing message stores for 7bit MUAs. If "old" 8bit MUAs can't handle a message/utf-8 part within an 8bit message/rfc822 it's no problem to be solved by the MDA:
There are tons of MIME types not supported by any given MUA, and maybe the user has helper applications to deal with some of these "unknown" (from the MUA's POV) MIME types.
To read message/utf-8 parts within a message/rfc822 behind a "UTF8SMTP ignorant" MUA a decent text editor with macros to decode QP or B64 should be enough.
_______________________________________________ IMA mailing list IMA at ietf.org https://www1.ietf.org/mailman/listinfo/ima