On Thu, Aug 13, 2009 at 6:50 PM, Angus Scott-Fleming<[email protected]> wrote: > GeoApps - Configuring Mail Clients to Send Plain ASCII Text > http://www.geoapps.com/nomime.shtml
Hopelessly out-of-date. Exchange 4.0 is the most recent it covers! And MIME is hardly a rarity these days. My apologies to those still using /bin/mail to read your email, but the world has moved on. Get with the times. :) If one wants to try and work around the Lyris problem, I'd say the first thing to do would be to look for a way to have Outlook/Exchange 2007 use quoted-printable rather than BASE64 encoding. Lyris doesn't seem to have a problem with quoted-printable. QP would also result in smaller messages, since most of the text is ASCII anyway. They'd also be mostly readable without decoding, which is useful for debugging mail issues. If that's not an option, the next thing I'd look for would be a way to turn off all the auto-replace features of Outlook/Word 2007. AutoText, AutoFormat, Smart Quotes, etc. If the message can be represented entirely using plain ASCII text, Outlook/Exchange might not feel a need to apply a transfer encoding. But really, Lyris should be fixed. (Or replaced with other list server software that isn't a perpetual source of trouble.) Unicode and BASE64 have very legitimate uses. These days, there is a much bigger online population of people and companies using names which can't be cleanly represented in ASCII. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
