The native clients I'm using are K-9 Mail, Google Inbox, and Gmail. When I get an HTML e-mail that I want to post to my blog, I forward it. Currently, I'm using Blogger for this since that workflow seems to reliably get the HTML up on my blog without any massaging on my part. I tried posting an HTML e-mail to WordPress in this manner, by forwarding it with Inbox, and the post was empty. I tried it with Gmail and got the same result. However, when I post using Gmail on a Web browser -- both Chrome for desktop and Chrome for mobile -- the message appear properly on WordPress.
I'm guessing that the native clients are not actually sending the message's assets (images, at least), but only the IMG tags, leaving it up to the recipient's client to load the assets.
My first question is, is this guess correct? My second question is, why do native clients behave this way? Is it a question of bandwidth, i.e., the cost of sending the assets themselves versus sending the IMG tags? My third question is, how can I get around this with a native Android client? Now that I know I can do this with Gmail on mobile Chrome, no problem, but it would still be nice to be able to do this offline.