WP Offload SES 1.6 uses the latest Amazon SES API v2 in order to increase the maximum size limit of messages from 10 MB to 40 MB.
📩 Larger Attachments
A little while ago, Amazon increased the maximum size limit for messages from 10 MB up to 40 MB. As a result we’ve had quite a few users of WP Offload SES contact us, confused as to why they still could not send emails with attachments larger than 10 MB in size.
The problem was that WP Offload SES was built using Amazon SES API v1, which means it could not take advantage of the increased size limit—until now. In version 1.6, we’ve upgraded to SES API v2 and now support message sizes up to 40 MB.
Stuck Queue & Failed Messages Explained
While investigating the changes needed to send emails with larger attachments, we also uncovered an explanation of why email queues have occasionally become stuck in previous versions of WP Offload SES.
Have you ever seen a list of outgoing emails stuck with a “Queued” status for some unexplained reason?
Eventually one email fails, allowing the following emails to finally get sent.
Inspecting the failed message provides no obvious explanation for the failure.
So you optimistically click Resend and cross your fingers…
…only to find that the retried message has failed yet again. 😞
Here’s what was happening. In addition to SES API v1 being unable to send emails with a size greater than 10 MB, the AWS SDK for PHP Version 3 bundled with the plugin was also having issues handling errors returned for larger messages. Further investigation revealed that fatal errors were being thrown due to memory exhaustion.
As 10 MB is Never Enough, especially when sending a bunch of Pictures of You, the cure is to upgrade to WP Offload SES 1.6 and retry sending the large message.
And as hoped, SES will Just Say Yes and send the over 10 MB message. 🎉
✅ Domain Verification Changes
With the upgrade to Amazon SES API v2, domain verification requirements have changed.
In WP Offload SES 1.5 and earlier, domain verification required a single TXT DNS entry to be created.
In WP Offload SES 1.6, domain verification now requires that three CNAME DNS records be created.
This new requirement only applies to new domains you wish to verify. Any previously verified domains or specific email addresses will continue to work with WP Offload SES 1.6.
As always, there’s a few other changes in the new release, including updates to the required version of WordPress and PHP, sanitization of broken Content-Type email headers created by 3rd party plugins, and other bits and bobs.
For a full list of new features, improvements, and bug fixes, see the 1.6 Changelog.
With WP Offload SES being quite the workhorse plugin that just sits there quietly doing its job as a core component of a site, we’re very careful with it. However, we do have some ideas on how to improve it, and will be actively engaging with our customers in the future to find out what they would like to see changed, and just as importantly, not changed.
Until then, we want to hear your thoughts on this release. Let us know on Twitter or in the comments below.