Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Well, I found out that this problem appears when you select the option “Use HTML content type”. If you don’t select it, the email is sent with both HTML and simple text. In this setting, <html> are used so the problem with the HTML_MIME_NO_HTML_TAG rule is no more. In my case I use WP Mail Smtp to send mail with SMTP rather than mail(). I don’t know if that makes any difference.

    What I didn’t realise is that the message body gets converted to HTML just like post and pages. If you use only one newline, it will not make a new paragraph, resulting in text being all in the same block. It doesn’t convert newlines to <br>s, it converts text blocks to <p>s. In my case I had to use double newlines to have it behave correctly.

    This post could have not been better. You clearly identified many shortcomings in the way the plugin handles email messages. I get a 2.9 in mail-tester.com, mainly because:

    FREEMAIL_FORGED_REPLYTO Freemail in Reply-To, but not From (which is actually a best-pratice, no fault here)

    HTML_MIME_NO_HTML_TAG HTML-only message, but there is no HTML tag. Your message should contain an <html> tag

    MIME_HTML_ONLY Message only has text/html MIME parts. You should also include a text version of your message (text/plain)

    These last two seem like easy fixes to me. Basically make sure the text only version is also included, and that the HTML is wrapped in <html> tags.

Viewing 2 replies - 1 through 2 (of 2 total)