ShapeLayout | Custom shaped layout for Android 自定义形状布局 | Android library

I've come up with such idea.

I have added Option Explicit to the top of your code. This is very helpful in finding compile-time errors.

Notice that the '

This ensures you have matched a style tag and not some tag that begins with style such as (I made up this tag name).

The problem you're hitting with MimeKit giving you an error about failing to parse the headers is due to the fact that your string is missing the message headers.

What you're effectively doing is asking a MIME parser to parse a message starting half way into the message. You're giving it an impossible task.

You need to combine the original message headers with the above string to produce the original (complete) message source before you can parse it.

Either that or you have to fake the original message headers so that things parse correctly.

Presumably you have the original message headers somewhere in your database?

Does the QuotedPrintableDecoder method need to come into play? I've reviewed http://www.mimekit.net/docs/html/Working-With-Messages.htm, but I'm hoping I don't have to manually traverse each part and there's still a way to grab just the message body.

There's generally no need to use any of the low-level decoders (or encoders) yourself.

There are multiple ways to get the message body:

1. Traversing the MIME tree manually (but in general I wouldn't recommend it), but to do this you really need to understand how MIME is structured and how common mail clients will structure their messages. It's not something I would generally recommend unless you are well-read on MIME. (Difficulty: Extreme)
2. Using a MimeIterator. For the most part, I wouldn't bother with this approach unless you want to manually traverse the MIME tree structure without using any sort of recursion. Where this class really comes in handy is if you are implementing something more akin to an IMAP server. Again, you need to understand how MIME works to really make use of this. See the documentation for a simple example on how to use this. (Difficulty: Extreme)
3. Using a MimeVisitor subclass to traverse the MIME tree structure. For a good example on how to do this, I would recommend taking a look at the HtmlPreviewVisitor class in the example in the documentation. This is probably the best way to do things if you want to "render" the message like a mail client might. (Difficulty: Moderate)
4. If all you want is the quick & dirty way of getting a message body and you don't care about trying to render the message the same way Outlook or GMail do, then you can use the MimeMessage.TextBody and/or MimeMessage.HtmlBody properties. (Difficulty: Easy Mode)

If I were you, I'd probably choose between the TextBody/HtmlBody properties and using something similar to the HtmlPreviewVisitor class in the example docs. They will be the simplest way to accomplish what you want to do.

you are right - mail-tester test looks very good! But you are testing for test message with very simplified content. Most likely your real mail send outs spam-classed by Google exactly due to mail HTML and/or text content. For example in your real mail exerpt the first thing I see i the subject 'test' which is itself provocative and even when you testing especially with real providers you should try to keep your test mail as real as possible starting even with subject line. Otherwise it can be something wrong or mismatching with subject, links and urls in body, words and phrases used, if html body matches text body well. These are enough reasons to decrease deliverability rating much enough. So please try to test one of real send outs mails which you mail to google and check mail-tester results again. Then you are welcome with more question! Regards!

It seems you'd to display the whole email message (email body), if so, uses </code> should be one solution.</p> <p>Check <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe#attr-sandbox" rel="nofollow noreferrer">MDN IFrame</a> on the details of property=<strong>srcdoc</strong>, and <strong>the browser compatibility</strong>.</p> <p><div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="false"> <div class="snippet-code"> <pre class="snippet-code-js lang-js prettyprint-override"><code>let testEmailBody = `<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri","sans-serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri","sans-serif"; color:windowtext;} .MsoChpDefault {mso-style-type:export-only;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.WordSection1 {page:WordSection1;} --> </style> <!--[if gte mso 9]><xml> <o:shapedefaults v:ext="edit" spidmax="1026" /> </xml><![endif]--> <!--[if gte mso 9]><xml> <o:shapelayout v:ext="edit"> <o:idmap v:ext="edit" data="1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=EN-US link=blue vlink=purple> <div class=WordSection1> <p class=MsoNormal> <o:p>Test Email &nbsp;</o:p></p> <p style="background-color:green;color:white">I am a test!</p> </div> </body> </html>` Vue.config.productionTip = false app = new Vue({ el: "#app", data: { emails: [ {'from':'stackoverflow', 'to': 'someone@test.com', 'body': testEmailBody}, {'from':'stackoverflow', 'to': 'someone@test.com', 'body': testEmailBody} ] } })</code></pre> <pre class="snippet-code-html lang-html prettyprint-override"><code><script src="https://unpkg.com/vue@2.5.16/dist/vue.js"></script> <div id="app"> <div> <table> <tr v-for="(email, index) in emails" :key="index"> <td>{{email.from}}</td> <td>{{email.to}}</td> <td><iframe :srcdoc="email.body">

Here is the script:

I was able to achieve the outcome, instead of converting the mails, store them to a S3 bucket and using a S3 trigger, invoke a Lambda function which forwards the mail content. To simplify the forwarding, I have used the NPM library aws-lambda-ses-forwarder, which does all the heavy lifting. Following code shows the logic for email forwarding.

Using the BeautifulSoup library, it is actually not too hard to parse the text. If you do not have the library, make sure you pip install bs4 first. After that, it shouldn't be too hard: