Send WordPress emails with Rabbitflare SMTP
Turn on Rabbitflare SMTP so password resets, sign-ups, admin notices and order emails arrive: what it sends, the limits, notice and reply addresses, and email credit.
8 min read Updated
Rabbitflare SMTP sends a site's own WordPress emails for you: password resets, new-account emails, account changes, admin notices and WooCommerce order emails. One click in the site's SMTP tab turns it on. There's nothing to set up: no passwords, no email service to sign up for and no DNS records to add. It's included with your hosting, within the limits below.
What it sends, and what it leaves to WordPress
| Sent through Rabbitflare | What that covers |
|---|---|
| Password resets | WordPress's and WooCommerce's “Reset your password” emails |
| New accounts | The welcome email with the link to set a password |
| Account changes | Email or password changed, and privacy requests |
| Admin notices | New users, new orders and updates, to the site's confirmed admin addresses only |
| Order emails | WooCommerce's order received, processing, completed, refunded, failed, cancelled, invoice and note emails |
Everything else is left to WordPress exactly as if Rabbitflare SMTP weren't there: contact forms, comment notices, newsletters and other marketing, and emails from any other plugin. Those are never handed to us. Attachments are never sent: an email that had one goes without it.
Turn it on
-
Open the site's SMTP tab
On the site's page, open SMTP. It lists what's sent and what isn't, the limits, and the sender your recipients will see.
-
Choose Turn on
Rabbitflare adds a small plugin to the site, in its
wp-content/mu-pluginsfolder. It takes about a minute, and the site keeps working throughout. From then on, the tab shows today's use, the last 30 days and every email with what happened to it.
It works on live sites on every server, those from Rabbitflare and the ones you connected yourself. A staging copy never sends through it, so turn it on for the live site. It needs a paid, active server (or an active plan for your own servers) and a confirmed account email address; it isn't part of the free trial.
What recipients see
- The sender: your site's domain as the name, for example “acme.com”, at an address of the site's own on Rabbitflare's sending domain. The tab shows the exact sender.
- A plain, tidy layout: the same for every site. The first line says which website sent it. A shop's own email design isn't carried over.
- Links only to your site: links to the site's own addresses stay; any other link is replaced by “[link removed]”. That keeps your emails from being used for phishing.
- A short footer: “Delivered by Rabbitflare”, and a link the recipient can use to report an email they didn't expect.
- A reply address, if you set one: see Reply address.
The limits
Strict limits keep every site's emails trusted by inboxes. An email over a limit isn't sent, and WordPress is told it couldn't be sent, with the reason.
| Limit | Included |
|---|---|
| Emails a day, per site | 50 |
| Emails a day in a site's first 14 days | 10 |
| Emails in any 10 minutes, per site | 5 |
| Emails a day for all your sites together | 150 |
| New addresses a day, per site (addresses the site hasn't emailed before) | 5 in the first 14 days, then 15 |
| To the same address, from one site | 3 an hour, 10 a day |
| To the same address, from all Rabbitflare sites together | 20 a day |
| Admin notices to confirmed addresses | 10 a day per site, on top of the rest |
| Recipients per email | 1: an email to several people goes as one email each (up to 3) |
| Subject and text | 150 characters, and 20,000 characters of text |
| Attachments | None |
| Links | Only to the site's own addresses, at most 10 |
“A day” is any 24 hours, and “an hour” any 60 minutes, not the calendar day. A busy shop can send more with email credit.
Admin notice addresses
Admin notices (a new user signed up, a new order came in, the site updated itself) go only to addresses you've confirmed, so nobody else can receive your site's admin emails. Your account's own address and your team members' addresses are always confirmed. In the SMTP tab you can add up to 5 more per site, such as a shop manager's:
- Under Admin notice addresses, enter the address and choose Add and send confirmation.
- We email it a link from Rabbitflare. It works once, for 48 hours.
- Once the link is opened and confirmed, the address gets the site's admin notices.
Your account can send 3 confirmation emails a day. If the site tried to send admin notices to an address that isn't confirmed, the tab lists it with a Send confirmation button. The site's admin email in WordPress (Settings › General) doesn't need to match.
Reply address
Without one, replies to your site's emails aren't delivered anywhere. To get them, set a Reply address in the SMTP tab, such as your shop's support address. It's confirmed the same way as a notice address, and used from the moment it's confirmed. Remove it and the site's emails stop carrying it at once.
Why an email wasn't sent
The SMTP tab lists the site's emails for 30 days, with what happened to each. When one isn't sent, WordPress shows the same reason as its usual “could not be sent” message. These are the reasons:
| What you see |
|---|
| Rabbitflare SMTP is switched off for the moment. WordPress was told the email couldn't be sent. |
| Rabbitflare SMTP isn't turned on for this site. |
| Rabbitflare SMTP needs a paid, active server and a confirmed account email address. |
| Email from this site is paused. Open the site's SMTP tab in Rabbitflare to see why. |
| Email from this site is stopped while its Rabbitflare SMTP plugin file is checked. |
| Email from this site is suspended. Contact Rabbitflare support. |
| Email is switched off for this account. Contact Rabbitflare support. |
| This site's plugin hasn't been checked recently, so nothing is sent until it is. |
| Rabbitflare SMTP only sends WordPress's own emails: password resets, sign-ups, account changes, admin notices and order emails. |
| This email couldn't be sent: its subject or text is too long, or not readable. |
| This address can't receive emails from this site. |
| This address bounced or reported an email before, so this site no longer emails it. |
| Admin notices only go to addresses confirmed in the site's SMTP tab in Rabbitflare. |
| This site has sent its most emails for 10 minutes. Try again shortly. |
| This site has sent its most emails for today. |
| This site is new to Rabbitflare SMTP and has sent its most emails for today. |
| This account's sites have sent their most emails for today. |
| This address has been sent its most emails from this site for an hour. |
| This address has been sent its most emails from this site for today. |
| This address has been sent its most emails for today. |
| This site has emailed its most new addresses for today. |
| This site has sent its most emails to its confirmed admin addresses for today. |
| Rabbitflare SMTP has reached its sending limit for today. Emails go out again tomorrow. |
| This site has used its included emails for today, and the account has no email credit left. |
| The email couldn't be sent just now. WordPress may try again. |
When email is stopped
Rabbitflare stops a site's email by itself when something looks wrong, and emails you to say why and what to do. The SMTP tab says it too.
- Paused when someone marks one of the site's emails as spam, when several go to addresses that don't exist (3 in 24 hours), when recipients report them, or when the site suddenly tries to send far more than usual. After a first pause you can use Turn on again once, an hour later, after fixing the cause: a contact form or sign-up page that emails strangers is the usual one.
- Stopped for a check the moment the Rabbitflare SMTP plugin file on the site changes. It's put back by itself; if the change wasn't ours, email from the site is then suspended.
- Suspended when the plugin file was changed by someone other than Rabbitflare, or by our team after a serious problem. Only our support team can lift it.
- Switched off for the account after a second pause within 30 days. Your sites keep working; their emails don't go through Rabbitflare until support switches it back on.
An address that marked one of your sites' emails as spam, or reported one, is never emailed again by your sites. An address that bounced is skipped for a while, and for longer if it bounces again.
More emails with email credit
Each site's first 50 emails a day are always included. A busy shop can send more with email credit: it pays for emails beyond the included ones, at the price per 1,000 shown in the SMTP tab, and your first top-up raises your limits. Clean sending raises them again:
| Step | Per site, a day | All your sites, a day | Per site, 10 minutes | New addresses a day | Reached |
|---|---|---|---|---|---|
| A | 200 | 500 | 20 | 100 | With your first top-up |
| B | 500 | 1,500 | 40 | 300 | After 14 days on A without a stop, with 500 emails sent |
| C | 1,000 | 3,000 | 60 | 600 | After 30 days on B without a stop |
Choose Add email credit under More emails in any site's SMTP tab, and pay from your wallet or by card. Credit is shared by all your sites, never expires, and can't be refunded or withdrawn. Every other rule on this page applies to paid emails too. Need more than step C? Ask our team.
So that the extra emails go only to real shops, email credit can be bought once all of these are true:
- Your account is at least 30 days old, and isn't in its free trial.
- A payment for your hosting was made at least 14 days ago, and wasn't refunded or disputed.
- Two-factor sign-in is on.
- Rabbitflare SMTP has been on for at least 7 days, with no stop on your account's email in the last 30 days.
The SMTP tab says which one is missing, if any.
The Rabbitflare SMTP plugin
The plugin holds no password and no key: it only hands WordPress's own emails to Rabbitflare, and leaves every other email alone. It's a must-use plugin: WordPress lists it under Plugins › Must-Use, and it can't be deactivated there. In WP Admin, Tools › Rabbitflare SMTP shows its latest results, and a notice tells administrators when an email wasn't sent.
Turn it off
Under Turn off in the SMTP tab, choose Turn off. The plugin is removed from the site and WordPress sends its emails as it did before. Turning it off doesn't lift a stop: a paused or suspended site stays so if you turn it on again.
Questions
I already use an SMTP plugin. Do I need this?
Not if your plugin already delivers every email well. An SMTP plugin replaces the way WordPress sends email, so while it's active, the site's emails don't reach Rabbitflare SMTP: the SMTP tab warns you when that's the case. Keep one or the other. If you switch to Rabbitflare SMTP, deactivate the SMTP plugin.
What about contact forms?
Contact-form emails are left to WordPress, because their text is typed by visitors. If the site needs them, an SMTP plugin connected to a mailbox, for example a Rabbitflare Mail mailbox with an app password (see mail apps), sends all of the site's emails, contact forms included. Rabbitflare SMTP then isn't needed on that site.
Can emails come from my own domain's address?
Not yet. The sender's name is your site's domain, at an address on Rabbitflare's sending domain, so you don't need to add any DNS records.
Why do my order emails look different?
Every site's emails use the same plain layout, so the shop's own email design isn't carried over. The order details are all there: products, prices and addresses, as text, with links back to your shop.