Test post

A couple of you have about the risk of content filtering with HTML.

The key to keeping your risk of filtering down is the actual content of your messages, not just sending them in plain text as opposed to HTML. An HTML message about a golf newsletter is going to be filtered far less than a plain text message about cheap pharmaceuticals or penny stocks.

When you’re creating your messages, whether you use HTML or not, take advantage of the SpamAssassin tool that’s integrated in your account. Check your scores and make any needed changes based on SpamAssassin’s criteria.

As long as you keep your SpamAssassin score low, and include a plain text version, you can send HTML messages without significantly increased risk of filtering.

A couple of you have commented about the risk of content filtering with HTML.

The key to keeping your risk of filtering down is the actual content of your messages, not just sending them in plain text as opposed to HTML. An HTML message about a golf newsletter is going to be filtered far less than a plain text message about cheap pharmaceuticals or penny stocks.

When you’re creating your messages, whether you use HTML or not, take advantage of the SpamAssassin tool that’s integrated in your account. Check your scores and make any needed changes based on SpamAssassin’s criteria.

As long as you keep your SpamAssassin score low, and include a plain text version, you can send HTML messages without significantly increased risk of filtering.