Working in WordPress support over the years has taught me a lot of important lessons both good and bad. First, you should always have a backup!
Second, and almost as important, you have to know that your emails are being delivered quickly and reliably to your members’ inboxes.
In all my years in support I’ve seen very few site owners who have given a second thought to how their emails are being sent out, where they’re being sent from, and what potential issues they could come up against by leaving WordPress emails as their default.
Don’t get me wrong, the fact that WordPress will almost always be able to send out emails without you having to so much as lift a finger to make it happen is incredible. But there are some potential issues that should be considered.
The Problem with WordPress Mail
Without getting too technical here, WordPress (by default) will attempt to send emails by using a local mail server when possible. This means 99% of the time your emails are coming from the same webserver your site is hosted on. That doesn’t sound so bad, but here are the issues that often get overlooked:
- Are you on a shared hosting server? If so, what have other website owners on the server done to tarnish its reputation with email providers?
- What history does your server’s IP address have with email block lists?
- Does your webhost allow you to customize the “From” email address and “From” name in outgoing emails?
- Does your webhost put limits on how many emails you can send per day/month? If so, what are those limits? How likely are you to reach them?
- What is the up-time of the mail server provided by your host and how quickly can/do they fix issues?
- What happens to emails that fail to send? Do they get retried — or just dropped?
- How many other users are sharing the mail server with you? How fast does the webhost serve up requests?
There are other issues, but these are the most common and are a really good starting point in determining if your email server is going to be reliable or not.
Consider, for example, that you’ve configured a Reminder email in MemberPress to notify members one week before their credit card expires. Now imagine that you have 800 people (a bit exaggerated, but not unbelievable for a large subscription site) whose credit cards will be expiring at the end of the current month.
On the day that the reminder gets triggered, MemberPress will send out 800 emails throughout the day to these members informing them that they need to update their credit card information.
Now imagine that your web host limits you to 300 emails per day, and on top of that, they drop any emails into a black hole after you’ve reached that limit. That means 500 people now have no idea that their credit cards need to be updated before their subscription will lapse!
Or, what if your mail server was put on a block list for many of the large email providers. How many of those 800 folks would never see that email because it’s been marked as spam?
You should seriously consider these issues if you want to save yourself a lot of customer support and financial headache. This is crucial if you’re running a membership site with something like MemberPress.
Your members will expect emails with instructions almost immediately after signing up, and they’ll no doubt want to be reminded before their subscription expires or auto-renews. If they don’t get reminded before getting charged you can guarantee they’re not going to be happy with you. And it’s never fun to get yelled at, period.
There is a Solution!
Right now you’re probably thinking, “Great! Another thing to stress and worry about.” But I have some good news: these issues can be avoided.
First, you want to install the WP Mail SMTP plugin. It fixes your email deliverability problems by reconfiguring WordPress to use a third-party SMTP provider when sending emails.
Second, you’ll need to choose your third-party SMTP providers. Some good ones include Mailjet, SendGrid, MailGun, and Amazon SES.
One great thing about most third party mailing services is that all emails and fail-to-send alerts are logged. If a customer complains about not receiving an email, check the log and see if there was an issue delivering their email. More often than not, the customer simply incorrectly entered their email address when signing up.
Installing a Third Party Email Service
MailGun and Amazon also have free tiers which you can use, but for this installation guide, I will be using SendGrid.
Step 1 – Signup For SendGrid
Head to https://sendgrid.com/user/signup and create your free account.
Step 2 – Tell WordPress to send emails via SendGrid
This sounds complex, but it’s really easy. I promise. Head to your WordPress Dashboard > Plugins > Add New. Now search for “SendGrid” and install the official SendGrid plugin.
After installing and activating the plugin, head to your WordPress Dashboard > Settings > SendGrid. Enter your username and password for the free SendGrid account you created, choose API method, and save the settings.
MemberPress will override the “Name” and “Sending Address” fields under “Mail Settings,” so there is no need to fill those out.
That’s it! You can now sleep well knowing that your emails will be delivered quickly and that SendGrid is dealing with all the stressful parts for you.
Great post Paul and it certainly makes a lot of sense to use a transactional email SMTP provider for the reasons you’ve pointed out. We’ve used sendinblue before which did a pretty good job and I believe Amazon ses is good also although we’ve never used the service.
Hello
Since sendgrid has much more complex email templates than you do I was wondering if it’s possible to create all the “Order receipt”, “renew credit card” etc emails in Sendgrid instead of Memberpress?
Or do you have to create all the emails in Memberpress and lett Sendgrid send them out?
Best
Gustav from NewLink
Hi Gustav 🙂
Yes, you can integrate MemberPress and Sendgrid via Integrately. Learn more at this page. Thanks!