"read msg" smart service with .msg to html confusing to AI in some instances

I have a subset of .msg files which when read with the read msg smart service, render in a tiny font with the .html output which results in AI being unable to interpret. 

Would I probably be better off running several reg ex statements to exclude tags that are confusing it and pasting in some style that would force the font, or just use the extracted (not the generated result document), or move it to PDF, or some different approach?

Regards,

Eric Casteel