A rock-solid setup for sending SMTP mail from your EC2 web server
(None of this is EC2-centric, but it’s particularly needed on EC2.)
A frequent topic of discussion on the EC2 forums is how to send email reliably, efficiently, and especially without it being marked as spam. I found that even with a valid SPF record most mail sent from an EC2 instance was marked as spam or silently discarded.
This is probably partly because of the lack of matching reverse DNS records. But spam filters can be a bit arbitrary and the easiest way is to relay outgoing mail through a good smtp provider. (I don’t recommend relaying outbound mail through Google Apps, they supposedly have a 500 messages/day limit according to many people on their forums, although I couldn’t find that published anywhere. UPDATE: The info is here, thanks John Ward.)
I have tried a couple of SMTP providers, and I recommend AuthSMTP. They are reliable, have good service, and our mail that’s delivered through them almost never gets marked as spam. Also, they have monthly quotas rather than daily, so you have a chance to increase it before you hit the limit.
Rather than deliver directly to the AuthSMTP mail server from your web app it’s a good idea to deliver to a local queueing mail server, which will forward via the AuthSMTP gateway. Your web app will deliver mail to localhost (or perhaps a dedicated instance if you prefer), port 25.
This has several advantages:
- Your web server can finish the request more quickly.
- There’s less chance that the mail server will be unavailable. At least the mail will be queued locally until the remote server becomes available again. AuthSMTP has proven to be quite reliable, but it has been unavailable on a couple of occasions.
- AuthSMTP limits the number of concurrent connections that you can make. You can easily configure your local mail server to limit the number of outgoing connections to the gateway.
Configuration
I recommend using Postfix, it’s fast, reliable and most importantly, easy to configure. Your Linux distribution will definitely have a Postfix package available (it comes pre-installed on EC2 on Rails). On Debian or Ubuntu install with:
sudo aptitude install postfix
Here’s the config file, /etc/postfix/main.cf:
myhostname = www.YOURDOMAIN.com mydomain = YOURDOMAIN.com myorigin = $mydomain smtpd_banner = $myhostname ESMTP $mail_name biff = no append_dot_mydomain = no alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases mydestination = localdomain, localhost, localhost.localdomain, localhost mynetworks = 127.0.0.0/8 mailbox_size_limit = 0 recipient_delimiter = + # SECURITY NOTE: Listening on all interfaces. Make sure your firewall is # configured correctly inet_interfaces = all relayhost = [mail.authsmtp.com] smtp_connection_cache_destinations = mail.authsmtp.com smtp_sasl_auth_enable = yes smtp_sasl_password_maps = static:YOUR_AUTHSMPT_USER_ID:YOUR_AUTHSMTP_PW smtp_sasl_security_options = noanonymous default_destination_concurrency_limit = 4 soft_bounce = yes
How simple is that?! Have you ever seen a sendmail config file?
soft_bounce is important because it means that postfix will queue the messages if they’re bounced by the remote gateway for any reason (this is only if it’s bounced by the gateway, not if it’s bounced by the destination server). This would usually be caused by some configuration problem like an authentication failure. If the message is bounced by the eventual destination server (e.g. the mailbox doesn’t exist or is full), or if the destination server can’t be contacted, your local server won’t know about it because the message has already been accepted by the gateway. (It’s probably a good idea to keep track of bounced messages returned by the eventual destination server, see “Don’t spoof the From field” below.)
default_destination_concurrency_limit is so you stay within AuthSMTP’s concurrent connection limit. If you have Postfix running on multiple instances you’ll need to adjust this accordingly.
To see mail that’s stuck in the queue:
mailq
Postfix will automatically try to resend it, but you can force it to be sent immediately using:
sudo postqueue -f
Monitoring
Of course you need to know if anything goes wrong with the mail delivery and it won’t be in your web app’s log. I use scripts in /etc/cron.hourly to check logs and mail me the output if there are errors. But when it comes you mail delivery failure you might have a bit of a chicken-and-egg problem: you can’t use postfix to send the mail if postfix is having problems. Here’s a simple ruby script to send emergency mail via a different mail server. It’s configured to use Google Apps (you’ll need to create a new account to send the mail from), if you don’t use Google Apps you can easily change this to use a different mail server.
Save this as /usr/local/bin/emergency_mail_sender:
#!/usr/bin/env ruby
# This is a simple script to send mail via an alternate server when there are
# errors with the normal queueing mail sender
# The subject is the first command-line arg and the body is received on stdin
#################################
from_address = "admin_mail_sender@YOURDOMAIN.com"
to_address = "admin@YOURDOMAIN.com"
smtp_server = "smtp.gmail.com"
smtp_port = 587
smtp_mail_from_domain = "YOURDOMAIN.com"
smtp_account_name = "admin_mail_sender@YOURDOMAIN.com"
smtp_password = "YOUR_PASSWORD"
smtp_authentication_type = :plain
debug = false
#################################
subject = ARGV[0]
body = $stdin.read
require 'rubygems'
require 'net/smtp'
require 'tlsmail'
exit if body.nil? || body == ""
msgstr = <<END_OF_MESSAGE
Subject: #{subject}
#{body}
END_OF_MESSAGE
Net::SMTP.enable_tls(OpenSSL::SSL::VERIFY_NONE)
smtp = Net::SMTP.new(smtp_server, smtp_port)
smtp.set_debug_output $stderr if debug
smtp.start(smtp_mail_from_domain, smtp_account_name, smtp_password, smtp_authentication_type) do |s|
s.send_message msgstr, from_address, to_address
end
Here’s a script that can be run by cron every hour to check for mail delivery problems, it uses the emergency_mail_sender script to notify you of the problem. It works on Ubuntu (but it needs the logtail package installed), it might not work on other systems. Save this as /etc/cron.hourly/check_mail_logs
#!/bin/sh hostname=`hostname -s` mailer = /usr/local/bin/emergency_mail_sender /usr/sbin/logtail -f/var/log/mail.warn | $mailer "$hostname: mail warnings" /usr/sbin/logtail -f/var/log/mail.err | $mailer "$hostname: mail errors" /usr/sbin/logtail -f/var/log/syslog | grep 'status=' | egrep -v 'status=sent' | $mailer "$hostname: undelivered mail"
SPF
Here’s your SPF record:
v=spf1 include:authsmtp.com include:aspmx.googlemail.com ~all
If you’re not using Google Apps to send mail for your domain remove include:aspmx.googlemail.com. If you want to create your own SPF record there’s a good SPF record generator at spfwizard.com.
Don’t spoof the From field
You should only send mail from somebody@yourdomain.com. If you try to send mail from somebody@pauldowman.com, for example, the receiver will see that pauldowman.com has an SPF record, and that it doesn’t authorize your mail server. Then into the spam folder you go.
To get around this you can send from something like noreply@yourdomain.com, and set the Reply-To header to somebody@pauldowman.com. You can even set the name in the from field, for example: “Paul Dowman via yoursite” <noreply@pauldowman.com>. The Reply-To header will make sure that most people’s replies go to the correct address, but a few will inevitably end up at noreply@yourdomain.com so it’s probably a good idea to set up an autoresponder at that address, or at least make sure the message bounces so the user eventually realizes the mistake.
