Posted over 5 years ago. Visible to the public. Repeats. Linked content.

Test your application's e-mail spam scoring with

You can use to check your application's e-mails for issues that might cause e-mails to be classified as spam.

They provide a one-time e-mail addresses that you can use to sign up etc. You can then check for scoring results of SpamAssassin and other potential issues.
You don't need to hit 10/10. Something around 9/10 is perfectly fine.


  • For password-protected staging sites you will get an error for links that can not be resolved. This is fine, simply check production once available.
  • As long as e-mails are sent with a sender address of the application's domain, our operations team will have configured your servers and DNS records to cover the most obvious cases (SPF records, reverse DNS lookup, etc). However, your application should provide plain-text bodies for HTML e-mails. This can be done automatically.
  • Free plan is limited to 3 e-mails per day.


Further reading

Does your version of Ruby on Rails still receive security updates?
Rails LTS provides security patches for old versions of Ruby on Rails (3.2 and 2.3).

Owner of this card:

Emanuel De
Last edit:
5 months ago
by Daniel Straßner
email, spam, score, testing
About this deck:
We are makandra and do test-driven, agile Ruby on Rails software development.
License for source code
Posted by Emanuel De to makandra dev
This website uses short-lived cookies to improve usability.
Accept or learn more