On the other hand, if HTML is excluded then the message gets through without scope for mischief.
If you're afraid of HTML, by all means please check your email from a sandboxed VM in the terminal. But some poor chump is still going to be toiling away to make the latest Pottery Barn newsletter look great on a Blackberry, so we'd might as well build better tools.
CSS can cause problems, too. @import could cause privacy issues, as could @font-face. If images are not pre-downloaded, @media and @page could reveal when you print a message and @supports could leak details about your mail client. `position: fixed` would need to be banned outright I'd think, if the message isn't sandboxed in an iframe.
HTML5 as a whole is designed for building applications, not for making pretty messages. You want to have a subset of HTML5, but not too strict of a subset. Some APIs (e.g., @font-face) probably can't be used as-is and need a replacement. And of course, it all needs to be somehow backwards-compatible.
* http://jdebp.eu./Proposals/gnksoa-mua.html#NoAutoFetchExtern...
I'm not holding my breath for something good to come out of this, though. This could just as easily be a terribly executed product. But I'll try to be an optimist, because what we have now is outright trash.