>For what it is worth... I just fired a few of my trashed messages through a >hack decoder I knocked up; and it is Base64 encoding as I suspected.
In the days of 7 bit ASCII base64 was a necessity today it is rank stupidity. >So... I have to assume some setting has been "improved" by the clowns that run >our IT services at work... >I'll need to see if I can revert this - though there may be some noise whilst >I test - apologies in advance! from http://support.microsoft.com/kb/323489 Base64 encoding in Exchange Server Base64 encoding is used in the following situations: If you send a message that contains characters that are outside the 7bit US-ASCII range. Exchange Server is a 7-bit Simple Mail Transfer Protocol (SMTP) transport. To send an 8-bit message, the message must be encoded in Base64, and then sent by using SMTP. [snip] May be your outlook (M$ outhouse) is sending in one of these char sets. If you send a message that uses characters from certain character sets in the message body. Messages that use character sets from the following code pages are encoded as Base64 messages when they are sent from an Exchange 2000 computer: Shift-JIS EUC-KR ISO-2202-JP BIG5 ISO-2202-KR GB18030 GB2312 _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
