amore ac studio: I bow to your superior knowledge. 
Anyway, lynx is about as innocuous as you can get in terms of web browsers posing security risks: I know it can’t fetch web bugs and it can’t run Java or JavaScript. The worst it can do is accept cookies, and that’s configurable with a command-line flag (or by running Guidescope and setting lynx to use your localhost:8000 proxy).
If you must use HTML, then why not build special pages and then send the recipient the URL and password?
By definition, it is. Email is an ASCII text medium.
Email – even HTML email and items with attachments and pictures are ASCII text. Have any of you ever wondered why large attachments freeze Outlook for a few seconds? Or why Entourage mutters about “encoding attachments”? This occurs because the email client is uuencoding everything that it sends. On receipt, it has to decode (uudecode) everything. Email systems are based on 7-bit characters. Since modern computers are all based on 8-bit characters, conversion has to be done so you don’t lose 12.5% of all the information.
On that note, even HTML email is straight ASCII text.
If you look at uuencoded data, you’ll see that it’s not human legible, but it will be comprised of ASCII text.
Well, that’s like saying even ASCII text is binary.
Email should not consist of codes that are designed to be interpreted as markup language.
AHunter3, for what it’s worth, I completely agree with you – I detest HTML/Rich-Text email myself. Except at work for internal-only communications where I can just embed an Excel sheet.