! Make no mistake. The use of ISO-2022-JP DOES violate RFC 822.
! RFC 822 specifies ASCII. ISO-2022-JP, as you say, is NOT ASCII.
If ISO-2022-JP encoded Japanese character is violating RFC 822,
uuencoded Japanese charcter will also violate it, right?
How about uuencoded binaries like images or sounds?
I guess they are not ASCII.
In a strict sense no.
So is QP or Base64.
Displaying ESC-code plain in file is asking for trouble in my
mind. There have been a plenty of "letter viruses" when a
special ESC-sequence did some magic gymnastics with a terminal
(VT100 usually) and was thus able to send commands for the user
to execute without user being able to intervent -> most news
and email clients will NOT let any ESCs go thru to the display..
(Be paranoid, rather than sorry.)
Sure. That WAS a reason.
What MIME created is STRUCTURE notation which can be used by
smart MUAs to analyze the email and pull out attached files,
switch character-sets, .. On overall give hints about the
processing.
The last one is least useful but harmless within MIME.
Masataka Ohta