Elastic Email
Elastic Email configuration screen

Elastic Email is a mail relay service. That is, instead of your website sending mail via its own SMTP server, outgoing email is directed through the Elastic Email service and out onto the internet. This module provides plug n' play integration with the Elastic Email service. Learn more at the Elastic Email site.

Why?

Elastic Email is of particular use to cloud-hosted websites. There are three very prominent reasons to use it:

  • Some cloud services (or rather, their IP address ranges) are blacklisted by anti-spam services because of the high volumes of spam emanating from their servers. For example: Amazon/AWS. That is to say, if you send email directly from AWS, there's a good chance it will be blocked by spam filters.
  • Some servers have restrictions on outgoing ports, i.e. SMTP. Your website may simply be unable to use SMTP. Elastic Email uses a REST-style API over HTTPS. So, all you need open is port 443, the standard HTTPS port.

But the main reason may be that you can be up and running in less than 5 minutes total. Really. You can even get an account that lets you send 1000 emails before you need to pay up. And there's no need to mess with configuring sendmail or postfix on your server: all configuration is done from one simple Drupal admin screen.

How?

It's a three-step process:

  1. Sign up for an Elastic Email account, by going to http://elasticemail.com and click on "Start Sending Mail"
  2. Once signed up, make a note of your API Key and your Elastic Email username (aka your email address), which you will need to configure the module
  3. Install and enable the elastic_email module
  4. Configure the elastic_email module with the username and API Key

And you're done. If you need more detail, take a look at README.txt in the module download.

Notes

  • The config screen has a handy "Test" function to check that you're correctly configured.
  • This module does not currently support sending attachments.
  • You should setup a Sender Policy Framework (SPF) record for your domain to authorize Elastic Email to send email on your behalf. See: http://elasticemail.com/api-documentation/sender-policy-framework

7.x-2.0 is here!

** NOTE **: Upgrading to 7.x-2.x release from 7.x-1.x will require disabling the module before upgrading as some paths have been updated to reorganise the files better.

We have an initial release for version 7.x-2.x of Elastic Email, which adds support for the following enhancements:

  1. Added a dashboard with over stats from your Elastic Email account
  2. Added a warning threshold for when the account credit is getting low
  3. Add facility to be able to set the channel for the site to help define what site has sent an email
  4. Provide ability to view the log (this only provides data for the last 30 days as this is the restriction of the Elastic Email API)
  5. Added the ability to set the contents of the test emails for greater testing

Roadmap

Elastic Email has quite a few APIs that could be used to enhance the integration of this module.
I am looking at adding these to the 7.x version. Here is the current plan for adding these features:

7.x-3.x - New Features

  1. #2292615: Provide list of blocked email addresses
  2. #2307357: View the status of every email sent
  3. #1820892: Subscriber list management

If you think that one of them should be higher up the list, then please +1 the feature and I can then reorder the priority list to focus on the popular enhancements.

Project Information

Downloads