Send your sites’ emails
Forms, orders, passwords: send WordPress emails through a real sending service, without FluentSMTP or WP Mail SMTP.
Included in the free plan.
On this page
Why#
Out of the box, WordPress sends its emails with the host’s mail() function. That server isn’t allowed to write on behalf of your domain: Gmail and Outlook often file these messages as spam, or refuse them. The usual fix is an SMTP plugin on every site. With Situnio, the connector takes care of it: plugins (Elementor, Contact Form 7, WooCommerce…) keep calling WordPress as before, nothing else changes for them.
Add a sending service#
- Open Email sending in the menu, then Add a sending service.
- Choose the Service: an SMTP server (your domain’s mailbox: Infomaniak, OVHcloud, Gandi…), or your Brevo, Mailjet, Postmark or Scaleway account.
- For these four services, keep API (recommended) in Sending mode: sending goes over HTTPS and also works with hosts that block SMTP ports.
- Fill in the requested fields (a line under the form says where to find them at the service), then click Add this service.
One service can serve all your sites. Credentials are encrypted at Situnio, sent only to the sites that use them, and never shown again. Only the organization’s owner and administrators add services.
Turn sending on for a site#
- In the site list of Email sending, open the site. The same settings are in the Emails tab of the site page.
- Choose the Sending service and the Sender address, on a domain verified with that service.
- Click Check and turn on: the site first connects to the service. If the service refuses, nothing changes and the message says why.
- Send a Test email: it leaves from the site itself, like its forms.
For several sites at once, select them in the list and use Send through a service on the selected sites: {domain} and {site} are replaced by each site’s domain and name. A plugin that wrote on the visitor’s behalf keeps their address as “Reply-To”: you can still answer them. To pick sites faster, filter the list by name, tag, status or sending service: Select all only ticks the sites shown.
Replace FluentSMTP#
On a site where FluentSMTP sends emails with an SMTP server, Brevo or Postmark, click Replace FluentSMTP (or Replace FluentSMTP on the selected sites in the list). Situnio takes over its settings as they are: the key stays on the site and is never sent to Situnio. The connection is checked, then FluentSMTP is deactivated.
Hand sending back to WordPress puts everything back as before: FluentSMTP is reactivated if it had been replaced. It also comes back if you remove the site from Situnio or deactivate the connector. Another sending plugin (WP Mail SMTP, Post SMTP…) is never deactivated for you: deactivate it in WordPress first.
Follow sending#
Each site counts its sent emails and its failures, whether sending goes through Situnio or not. Latest failures shows, for each one, the recipient, the subject and the server’s answer, read on the site when you open the page. If emails fail on a site, the dashboard says so and the owner and administrators receive an email, at most once a week for the same site. At the top of the page, the sites with failures in the last 24 hours are listed with the server’s last answer and its likely cause (credentials refused, sender address refused, recipient blocked by the service…); the Failures in the last 24 hours status groups them in the list. The alert only counts failures since the last email that went out correctly and since the last change of service: a successful send clears it, and a failure of the former way of sending no longer triggers it.
In client reports#
The Email sending section of client reports gives, over the period, the number of emails sent and of failures, with a calendar showing how many emails went out each day (in red, days with at least one failure). Only figures: never a recipient or a subject. It only appears if the site sent emails during the period; in an appearance already saved, tick it.
Still have a question? Write to us.