Email

Tips & tricks: Avoiding Gmail spam filtering when using Ruby on Rails Action Mailer

It has become clear from our support logs that a lot of developers use Action Mailer to send emails. If you are one of these developers you should know that there is one issue that we have seen repeatedly which will cause your emails to get filtered as spam by Gmail: malformed message-ID. This also may occur with other libraries but we see this issue mostly with Action Mailer.

It has become clear from our support logs that a lot of developers use Action Mailer to send emails. If you are one of these developers you should know that there is one issue that we have seen repeatedly which will cause your emails to get filtered as spam by Gmail: malformed message-ID. This also may occur with other libraries but we see this issue mostly with Action Mailer.

We created our REST API so that you don’t have to worry about technicalities like these (we set a valid message-ID by default) but we understand that you may want to use the tools you are already familiar with.

If you want to use Action Mailer with Mailgun, it’s pretty easy to get started:

config.action_mailer.delivery_method = :smtp config.action_mailer.default_charset = "utf-8" config.action_mailer.perform_deliveries = true config.action_mailer.raise_delivery_errors = true config.action_mailer.smtp_settings = { :authentication => :plain, :address => "smtp.mailgun.org", :port => 587, :domain => "my-mailgun-domain.com", :user_name => "postmaster@my-mailgun-domain.com", :password => "my-password" }

The issue is that if you do not specify the message-ID, Action Mailer populates this header with a default value which may not be a valid message-ID. In addition, if you are connecting to an SMTP relay, that message-ID probably does not reflect the domain that is actually sending the email. It may say something like “<[uid]@localhost.localdomain>”.

Gmail is very strict about making sure that the message-ID in the MIME headers follows RFC 2822and that the domain in the message-ID is the same as the sending domain.

According to the RFC the message-ID should have the following format: “<[uid]@[sendingdomain.com]>”

There is a thread on Stack Overflow about how to set the message-ID in Rails, see example excerpt below:

require 'digest/sha2' class UserMailer < ActionMailer::Base default "Message-ID"=>"#{Digest::SHA2.hexdigest(Time.now.to_i.to_s)}@yourdomain.com" # ... the rest of your mailer class end

So, make sure to test that the message-ID is getting set correctly or Gmail will junk your emails!

Happy emailing!

Mailgunners

Sign Up

It's easy to get started. And it's free.

See what you can accomplish with the world’s best email delivery platform.

Related readings

Which SMTP port should I use? Understanding ports 25, 465 & 587

Which SMTP port should you use — port 25, port 465, or port 587? Click to learn more about Mailgun's guide to understanding SMTP ports...

Read more

Tips & tricks: Scheduling email delivery

It’s always fun chatting with customers about what they like about Mailgun (and what they’d like to see improved ).

Read more

How to quickly bake Mailgun with PHP

When I started coding, I remember debating whether I would want to learn ASP.NET vs PHP. I read thousands of bulletin boards on threads about each language to help me make my decision.

Read more

Popular posts

Mailgun iconSee what you can accomplish with the world's best email delivery platform. It's easy to get started.Let's get sending
CTA icon Mailgun Icon