though, and your delusions will quickly be shattered. So glad this helped sort things out for you, Dave. Yes, a world where everyone uses Chrome for browsing and Mac Mail for email would be nice! And, I remember having to correct a site once in IE6 (this was a while ago) because director in a bank was using it -- they weren't allow to update their own software because of the security implications! Some good news, Microsoft posted its first ever quarterly loss since they went public in 1986. Perhaps now they may take note and catch up with everyone else by producing standards compliant software.... or go bust! We live in hope!! You need to use appropriate "web safe fonts" and have a good font stack. Baskerville may not be resident on the recipients machine therefore it defaults to the next one down in the font stack until it matches a font resident on the recipients machine. http://cssfontstack.com/ I agree with what Christopher says here. I would use websafe fonts for the main body text of the email: Times, Georgia, serif, for example and then images for headings with the client's Baskerville. But I would try to persuade the client against this as much as possible. i! I have a report in SAP that sends an email with an html table. The table and all of its content is showed correctly in most of the emails except for outlook. It's not an error in the ABAP code, which means