How to Configure Post SMTP with Brevo (formerly SendinBlue) and Other SMTP Services

Many WordPress site owners rely on the Post SMTP plugin to ensure their website emails are delivered reliably. A common point of confusion arises when integrating with specific email service providers, especially after a major change like SendinBlue rebranding to Brevo. This guide will walk you through the manual SMTP configuration process for Brevo and explain how to handle similar setups with other services.

Why Manual SMTP Configuration is Necessary

The Post SMTP plugin offers a setup wizard that can automatically configure some popular email services via their API. However, not all services are integrated this way. For providers like Brevo, Elastic Email, MailerSend, and SMTP2GO, a manual SMTP configuration is the primary method of connection. This process is just as secure and effective; it simply requires entering the server details yourself instead of having the plugin do it automatically through an API.

Step-by-Step: Manual Brevo (SendinBlue) SMTP Setup

Following the rebrand from SendinBlue to Brevo, it's crucial to use the updated server addresses. Here’s how to configure it manually in Post SMTP:

1. Log into your WordPress admin dashboard.
2. Navigate to Post SMTP > Settings.
3. Click on the "Account" tab.
4. For the transport type, select "Other SMTP".
5. In the SMTP Settings section, enter the following details:
   • SMTP Host: smtp-relay.brevo.com (Note: This has changed from smtp-relay.sendinblue.com)
   • SMTP Port: 587 (TLS) or 465 (SSL)
   • Encryption: Choose TLS or SSL to match the port you selected.
   • Authentication: Set this to On.
   • Username: This is your Brevo account login email address.
   • Password: This is NOT your regular Brevo account password. You must use an SMTP Key, which you can generate from your Brevo account under SMTP & API section.
6. Click "Save Changes".
7. Run the connection test to confirm your settings are correct.

Is "Plain" Authentication Secure?

When configuring manually, you may see an authentication option. Using "Plain" authentication over a TLS-encrypted connection (port 587) is considered secure. The encryption layer protects your login credentials during transmission.

What About API Integration and Other Services?

Based on community feedback on the WordPress.org support forums, the development team behind Post SMTP has indicated they are working on or considering native API integration for several services, including Brevo, Elastic Email, and MailerSend. These features are typically added to the plugin's roadmap and released in future updates.

For other services like Amazon SES, a dedicated extension has been in development. Users have reported being invited to beta test this functionality.

Solution for Hitting Free Account Limits

A frequently asked question is about managing the sending limits of free tiers from providers like SendGrid or Brevo. While Post SMTP does not currently have a feature to automatically rotate through a list of primary connections based on quota, it does offer a robust Fallback feature.

You can configure a secondary SMTP account (e.g., from a different provider) in Post SMTP Settings > Fallback. If an email fails to send through your primary connection—for example, if a quota is exceeded—the plugin will automatically attempt to send it using the fallback account. This is an effective way to increase overall delivery reliability.

Conclusion

Configuring Post SMTP manually with Brevo or other SMTP providers is a straightforward process that ensures reliable email delivery from your WordPress site. Always remember to use the correct SMTP server address and generate a specific API/SMTP password from your email service provider instead of using your main account password. For the latest information on new API integrations, keep an eye on the official plugin changelog.