Brevo (formerly Sendinblue)
On this page
Connect CRM-NG SMTP to Brevo with a v3 API key and an authenticated domain, or use Brevo's SMTP relay instead.
This guide shows you how to send your WordPress email through Brevo, the service previously called Sendinblue. Brevo suits small and growing sites: it has a free plan with a daily sending limit and no card needed to start. It also covers how to use Brevo's SMTP relay if you prefer SMTP to the API.
The Brevo mailer sends through Brevo's API with a v3 API key. You also authenticate your domain in Brevo so receivers trust your mail.
Before you start
- A Brevo account (sign up at
https://www.brevo.com/). New accounts may need to finish a short profile and activation check before sending. - A domain you control, with access to its DNS records.
- Administrator access to your WordPress site.
Step 1: Add and authenticate your domain
- Sign in to Brevo
Go to
https://app.brevo.com/and sign in. - Open the domains page
Open the account menu (your name, top right) and choose Senders, Domains & Dedicated IPs, then the Domains tab.
- Add your domain
Choose Add a domain, enter it, and pick the option to authenticate it yourself by adding DNS records.
- Publish the records
Brevo lists a Brevo code (TXT), a DKIM record and a DMARC suggestion. Add them at your DNS provider exactly as shown.
- Authenticate
Return to Brevo and press the button to check the records. The domain should show as authenticated.
- Add a sender
On the Senders tab, add the address you will send from, for example
hello@yourdomain.com.
See Adding DNS records for help with DNS.
Step 2: Create a v3 API key
- Open SMTP & API
In the account menu, choose SMTP & API, then the API Keys tab (the direct address is
https://app.brevo.com/settings/keys/api). - Generate a key
Choose Generate a new API key, name it after your site, and create it.
- Copy it
Brevo shows the full key once. Copy it now.
Authorised IPs
Brevo can refuse API calls from IP addresses it does not know. If you turn on this protection (look for Authorised IPs under the account's security settings), add your web server's IP address there, or sending will fail.
Step 3: Connect in CRM-NG SMTP
- Choose the mailer
In WordPress, open CRM-NG SMTP → Settings → General and set Mailer to Brevo.
- Paste the key
Paste the key into API Key.
- Enter the sending domain
Type the domain you authenticated into Sending Domain, for example
yourdomain.com. CRM-NG SMTP uses it for the domain check after a test email. - Set the sender
Set From Email to the sender address you added in Brevo and set From Name. Tick Force From Email if other plugins change the sender.
- Save
Press Save Settings.
SMTP
You can send through Brevo's SMTP relay with the Other SMTP mailer instead of the API. This helps when your host blocks outgoing API calls but allows SMTP, or when you want one set of SMTP details for several tools.
- Find your SMTP details
In Brevo, open SMTP & API and the SMTP tab. Note the server (
smtp-relay.brevo.com), the port (587) and your login, which looks like an email address and is different from your account email. - Generate an SMTP key
On the same tab, generate a new SMTP key and copy it. This key is the password. It is not your Brevo account password and not the API key.
- Choose Other SMTP
In WordPress, open CRM-NG SMTP → Settings → General and set Mailer to Other SMTP.
- Enter the server
Set SMTP Host to
smtp-relay.brevo.com, Encryption to TLS, and SMTP Port to587. - Sign in
Turn on Authentication, put your Brevo login in SMTP Username and the SMTP key in SMTP Password.
- Save
Press Save Settings.
Brevo may need to activate SMTP on your account before the relay accepts mail. More about the fields: Other SMTP.
Send a test email
Open CRM-NG SMTP → Tools → Email Test, enter your address in Send To, and press Send Email. You can also find the message under transactional logs in Brevo. See Sending a test email.
The test page's domain check looks for sendinblue.com in your SPF record. Brevo's current setup relies mainly on DKIM and DMARC, so follow the records Brevo shows you; a warning about SPF alone does not mean sending is broken.
Troubleshooting
- Brevo has not verified the account, or your server's IP is not authorised: Unauthorized: not verified or IP not authorized
- The API key is wrong or deleted: Unauthorized: key not found
- The SMTP relay is not switched on yet: SMTP account not activated
- Brevo suspended the account: Account blocked
- The daily limit is used up: Email sending limit reached
- SMTP sign-in fails: 535 Authentication failed
- Mail arrives in spam: Emails landing in spam
