Setting Up Site Emails With Any SMTP Provider For WordPress On xCloud
Updated November 15, 2026 · 6 min read
WordPress frequently requires sending site emails to you or your users, known as transactional emails. These may include admin notifications, new user signups, password resets, and form submission emails from form plugins. At times, WordPress’s default email delivery system may fail, leading to potential issues like emails being flagged as spam or failing to reach their intended recipients.
xCloud does not configure your server to send or receive emails. Instead, we recommend using external email-sending services like Mailgun or Amazon SES for handling outgoing emails. Unlike traditional shared hosting, cloud servers do not come with a built-in email solution. We strongly advise against setting up an email server on the same server hosting your websites for security and performance reasons. Instead, you can choose from reliable hosted email services such as GSuite, Rackspace, Zoho, or set up an open-source email server solution like iRedMail if needed. It’s essential for WordPress sites to have a third-party SMTP service in place to send administrative and transactional emails, ensuring full functionality.
Due to its focus on optimal performance and security, xCloud provides email services on its own. You can send up to 100 emails for free per team with the xCloud Managed Email services. Plus, there are multiple plans to purchase 1000-8000 emails with a minimal cost. Web hosting servers are not optimized for sending emails, and you may also want to avoid running your own mail server.
However, if you want to set up site emails with any SMTP provider, we recommend using reliable email-sending services like Mailgun, SendGrid, Elastic Email, etc., which ensure that site emails are efficiently sent and delivered to recipients.
Two providers have their own step-by-step guides: Mailgun and toSend. toSend is built into the provider list, so you only paste its sending API key; xCloud fills in the host, port and username for you.
xCloud can streamline the delivery of transactional emails for your website by integrating any SMTP provider with FluentSMTP. It is a popular tool for managing SMTP services.
Note: If the CNAME record verification fails, that means your domain is not added to the Elastic email.
This usually happens when the domain already exists on Elastic Email (maybe he was using Elastic Email on other platforms).
Thus, always make sure that you have removed the existing domain from Elastic Email. Then you can use the retry button, it will automatically add the domain and verify the CNAME record.
Here is our detailed documentation on how you can configure any SMTP provider for site emails in the xCloud environment.
Step 1: Log In To SMTP Provider Account
Log in to your SMTP provider account and collect your login credentials (username and password), SMTP Host, and SMTP Port for using it in the xCloud mail integration.
Step 2: Add SMTP Provider For Site Emails
Once you are done collecting your SMTP details for Mailgun, it’s time to add the SMTP service as the email provider in xCloud. From your xCloud dashboard, navigate to My Profile → Integrations → Email Provider. You need to integrate your account domain with the credentials by clicking the ‘Add New Provider’ button.

Once you hit the ‘Add New Provider’ button, you will see a pop-up asking you to select the email provider, SMTP username, and SMTP password.

Select Other as the provider, and input your SMTP Host, SMTP Port, SMTP Username and SMTP Password. The email provider will be added instantly.
Step 3: Add Email Service Provider To Site
After adding the SMTP provider to integrate your xCloud environment, you just need to add the email provider to the site. Go to ‘All Sites’ and choose your website to add the email provider. Select your site and navigate to the ‘Email Config’ tab → ‘Mail Delivery’ addon from the dropdown.

Now select your domain from the ‘Email Provider’ options, set the sender’s name in the ‘From Name’ field, and input your email sender’s address in the ‘From Email’ field. Once done, hit the ‘Save Changes’ button.
💡To set up a professional email address with your custom domain, get a subscription for the xCloud MailBox Addon in just a few clicks.
That’s how easily you can configure any SMTP provider for site emails for xCloud environment to streamline the email delivery process of transactional emails.
Check and test site email from xCloud
After you save a provider on a WordPress site, the FluentSMTP panel below the Mail Delivery form lets you check FluentSMTP and send a real test email without opening WordPress admin. It works the same for every provider you can pick on this page, including Mailgun, SendGrid, toSend and any other SMTP service. Both buttons stay disabled until a provider is saved on the site. The panel only appears on WordPress sites.
Step 4: Check FluentSMTP
On your site, open ‘Email Config’ → ‘Mail Delivery’, scroll down to the FluentSMTP panel and click ‘Check FluentSMTP’.

xCloud reads the result from FluentSMTP on the site and shows:
- The connection: the sender address, the provider type and a ‘Settings OK’ or ‘Needs attention’ badge. When a connection needs attention, FluentSMTP’s reason appears under it.
- Sent and Failed: counts from the FluentSMTP email log on the site. If the site sends through xCloud Mail Delivery, Email Logs also shows each email’s status and the reason when it bounced.
- The FluentSMTP version installed on the site.
For SMTP providers, FluentSMTP checks the saved settings, not a login to the provider. ‘Settings OK’ does not prove the provider accepts your mail, so send a test email (Step 5) to confirm it. If a connection shows ‘Needs attention’, or the panel says FluentSMTP has no connection configured, click ‘Save Changes’ in the Mail Delivery form above to write the provider to FluentSMTP again, then check again.
Step 5: Send a test email
Under ‘Send Test Email’, enter an inbox you can open in ‘Send To’ (it starts with your account email) and click ‘Send Test Email’. The note under the field shows the address the test is sent from, which is the ‘From Email’ you saved.

xCloud runs FluentSMTP’s own test on the server, as the site’s user, through the provider saved on the site. The result line under the button is the provider’s real answer:
- Green: “Test email sent to …”. The provider accepted the message. Check the inbox (and the spam folder) and your provider’s delivery log.
- Red: “The test email was not sent:” followed by the reason the provider or FluentSMTP gave, for example a rejected login or a refused sender. When the provider refuses the message itself, xCloud also reminds you to check that the domain of your ‘From Email’ is a verified sending domain in your provider.
Fix the cause in your provider or in the Mail Delivery form, click ‘Save Changes’, and send the test again. If the FluentSMTP status is already on screen, its Sent and Failed counts refresh after each test.
If the check or test cannot run
| Message in the FluentSMTP panel | What to do |
|---|---|
| FluentSMTP is not active on this site. | Click ‘Save Changes’ above. Saving the provider installs and activates FluentSMTP again. |
| FluentSMTP on this site is older than 2.3.0. | Click ‘Save Changes’ above. Saving the provider updates FluentSMTP, because the check and the test use WP-CLI commands that ship with FluentSMTP 2.3.0. Then try again. |
| Too many test emails. / Too many checks. | Wait a minute. xCloud allows five test emails and ten checks per minute for your account. |
| Could not reach the server … | The server did not answer. Make sure it is connected in xCloud and try again in a minute. |
For a full walkthrough of one provider, see Configure Mailgun for site emails. To send through xCloud’s own service instead of an outside provider, see the Mail Delivery addon guide. If you want WordPress to use the server’s default mailer, read using the default wp_mail or PHP mail on an xCloud server.
Frequently asked questions
Does ‘Settings OK’ mean my site emails are being delivered?
No. For SMTP providers, FluentSMTP checks the saved settings, not a login to the provider. Send a test email from the FluentSMTP panel to confirm the provider accepts the message, then check your inbox and the provider’s delivery log.
Why does xCloud say FluentSMTP on my site is older than 2.3.0?
Check FluentSMTP and Send Test Email use WP-CLI commands that ship with FluentSMTP 2.3.0. Click ‘Save Changes’ in ‘Email Config’ → ‘Mail Delivery’: saving the provider updates FluentSMTP on the site. Then run the check or the test again.
Does the test email work with Mailgun, toSend or my own SMTP server?
Yes. The test uses whichever provider is saved on the site and sends through FluentSMTP from the saved ‘From Email’, so it works the same for every provider in the list.
If you run into any issues while setting up or testing site emails, feel free to reach out to our support team.