How to Set Up Brevo SMTP for Safe Email Sending

Your WordPress emails keep landing in spam folders, right? Or worse, they’re not sending at all. You’re losing customers because order confirmations vanish into the void, and password reset emails never show up. Here’s the fix that actually works.

Brevo SMTP changes how your website sends emails by routing them through professional email servers instead of your basic hosting account. This switch takes about 10 minutes to set up and immediately fixes most email delivery problems. Your emails start reaching inboxes, bounce rates drop, and customers actually receive their receipts and notifications.

What You Learn in This Guide

This guide walks you through setting up Brevo SMTP from start to finish. You’ll understand what SMTP actually does and why your emails fail without it. We’ll cover the exact steps for WordPress setup, including screenshots and testing procedures.

You’ll learn how Brevo SMTP connects with WooCommerce, Shopify, and other platforms. We’ll show you which ports to use, where to find your credentials, and how to test everything works. Plus, you’ll get fixes for common errors that stop emails from sending.

The best part? You can start with 300 free emails per day. That’s enough for most small businesses to test the system before upgrading. No credit card needed, no complicated contracts.

What Is Brevo SMTP? (Direct Answer First Sentence)

Brevo SMTP is a dedicated email relay service that sends your website’s system emails through Brevo’s professional servers instead of your hosting provider’s basic mail function.

Think about what happens when someone fills out your contact form. Without SMTP, your hosting server tries to send that email directly. Most hosting servers aren’t set up for email delivery, so messages get flagged as spam or blocked completely. It’s like trying to deliver mail without going through the post office.

Brevo’s SMTP relay works differently. When someone triggers an email on your site (password reset, order confirmation, contact form submission), that message goes to Brevo’s servers first. These servers have established reputations with email providers like Gmail and Outlook. They handle authentication, spam filtering, and delivery optimization automatically.

The technical side stays simple. You get an SMTP host address, choose a port number, and create an API key. These three pieces connect your website to Brevo’s email infrastructure. Once connected, every automated email from your site routes through Brevo’s system.

Real examples show why this matters. Your WooCommerce store sends order confirmations that customers actually receive. Contact form submissions reach your inbox instead of disappearing. Password reset emails arrive within seconds, not hours. Member registration emails bypass spam filters completely.

The free plan gives you 300 transactional emails daily through SMTP. That covers password resets, order confirmations, shipping notifications, and admin alerts. Marketing emails count separately if you use Brevo’s campaign features. Paid plans remove the daily cap and charge based on monthly volume instead.

How Brevo SMTP Works (Direct Answer First Sentence)

Brevo SMTP works by authenticating your website with a secure API key that grants permission to send emails through Brevo’s mail servers.

The process starts with your SMTP host – that’s the server address Brevo provides in your dashboard. This address tells your website where to send outgoing emails. Instead of using your hosting provider’s mail server, you’re pointing to Brevo’s professional infrastructure.

Port selection comes next. Brevo supports three main ports: 587, 465, and 2525. Port 587 handles standard TLS encryption and works for most setups. Port 465 uses SSL encryption for older systems. Port 2525 acts as a backup when hosting providers block the standard ports. Most WordPress sites use 587 successfully.

Your API key acts like a password that proves your website has permission to use Brevo’s servers. This key gets generated once in your Brevo account, and you can’t view it again after creation. Copy it immediately and store it somewhere safe. The key contains authentication credentials that identify your account and track usage.

The security layer protects your emails during transmission. TLS encryption scrambles the message content while it travels from your server to Brevo’s. This stops hackers from intercepting sensitive information like order details or login credentials.

Here’s the path your email takes: Your website triggers an email event (like a new order). The email plugin connects to Brevo’s SMTP server using your credentials. Brevo verifies your API key and checks the sender address. The message gets processed through spam filters and reputation checks. Finally, Brevo delivers the email to the recipient’s mail server with proper authentication headers.

Brevo’s spam filtering happens automatically. Their system checks your email content, sender reputation, and recipient engagement. Messages that look suspicious get flagged before sending. This protects your sender reputation and keeps delivery rates high.

Where to Find Your Brevo SMTP Settings

Start by logging into your Brevo dashboard and clicking on your account name in the top right corner. Select “SMTP & API” from the dropdown menu. This page shows everything you need for SMTP setup.

The API keys section appears at the top of the page. Click “Create a new API key” and give it a descriptive name like “WordPress SMTP” or “WooCommerce emails.” The system generates a unique key string that looks like random letters and numbers.

Copy this key immediately. Brevo shows it only once for security reasons. Paste it into a text file or password manager right away. If you lose the key, you’ll need to generate a new one and update all your connected apps.

Your SMTP server details appear below the API section. The server hostname stays the same for all accounts (shown as smtp-relay in most documentation). Note the recommended ports: 587 for TLS, 465 for SSL, or 2525 as an alternative. These numbers tell your email plugin how to connect securely.

Account restrictions show up as warnings if they exist. New accounts might have sending limits or require domain verification. Check for any yellow or red notices about your account status. Unverified accounts can’t send emails until you confirm your sender domain.

The username field typically matches your Brevo account email. Some older accounts might show a different SMTP identity. Write down whatever username appears in your settings. You’ll need this along with your API key for authentication.

Screenshot guidance helps when you can’t find settings. Look for sections labeled “Transactional,” “Developers,” or “Email API” if the SMTP menu isn’t obvious. The layout changes occasionally, but API keys always live in the account or developer settings area.

Save all these details in one place: SMTP server address, port number (usually 587), username, and API key. You’ll enter these exact values into your WordPress plugin or email application.

How to Set Up Brevo SMTP in WordPress

You set up Brevo SMTP in WordPress by installing an email plugin and entering your Brevo credentials into the plugin settings.

First, install a compatible SMTP plugin. WP Mail SMTP and Fluent SMTP both work perfectly with Brevo. From your WordPress dashboard, go to Plugins > Add New. Search for “WP Mail SMTP” and click Install Now, then Activate. The free version handles basic SMTP setup just fine.

After activation, find WP Mail SMTP in your left sidebar menu. Click Settings to open the configuration page. The setup wizard might appear automatically for new installations. Skip it and go straight to the settings page for more control.

In the Mail settings, look for the “Mailer” section. Choose “Other SMTP” from the dropdown list. Some versions show “Sendinblue” or “Brevo” as a direct option. Either works, but “Other SMTP” gives you more flexibility with port settings.

Now enter your Brevo SMTP details. Set the SMTP Host to the server address from your Brevo dashboard. Choose port 587 for Encryption type TLS. Port 465 works with SSL if your host blocks 587. Toggle “Authentication” to ON since Brevo requires login credentials.

Fill in your SMTP Username (usually your Brevo account email). Paste your API key into the SMTP Password field. Yes, the API key goes in the password box – that’s not a mistake. The key acts as your password for SMTP authentication.

Configure your From Email address next. This must match a verified sender in your Brevo account. Use your business email, not a free Gmail or Yahoo address. Add your From Name – typically your business or website name. Check “Force From Email” to override plugin conflicts.

Save your settings and run a test. WP Mail SMTP includes an Email Test tab. Enter your email address and click “Send Email.” Check your inbox within a minute. The test message should arrive with proper headers showing it came through Brevo’s servers.

Common setup problems have quick fixes. If test emails fail, verify your API key is correct. Check that port 587 isn’t blocked by your hosting provider – try 2525 instead. Make sure your sender email matches exactly what’s verified in Brevo. WordPress multisite installations might need network-wide plugin activation.

Contact form emails should start working immediately. Test your forms after SMTP setup to confirm messages reach your inbox. Check that admin notifications, password resets, and user registration emails all send properly through the new configuration.

SMTP Setup for WooCommerce Emails

WooCommerce uses the same SMTP setup as WordPress, so all your store emails automatically send through Brevo once SMTP is active.

Your WooCommerce installation doesn’t need separate configuration. The SMTP plugin you installed for WordPress handles all system emails, including every WooCommerce notification. This means order confirmations, shipping updates, refunds, and inventory alerts all route through Brevo’s servers automatically.

Order receipts benefit most from SMTP delivery. Customers expect instant confirmation after purchasing. Without SMTP, these critical emails often land in spam or never arrive. Brevo’s infrastructure ensures customers see their receipt within seconds of ordering. The professional delivery makes your store look legitimate and trustworthy.

Refund notifications work the same way. When you process a refund in WooCommerce, the system triggers an automatic email to the customer. SMTP routing guarantees these sensitive communications reach the right inbox. Customers stay informed about their refund status without wondering why they haven’t heard back.

Shipping emails become reliable with proper SMTP. Whether you manually update order status or use automation, shipping notifications go through Brevo. Customers track their packages without emails getting lost. You reduce support tickets asking about order status since notifications actually arrive.

Admin alerts reach you consistently too. Low stock warnings, new order notifications, and payment confirmations hit your inbox reliably. You won’t miss important store activity because emails got filtered as spam. Every backend notification flows through the same SMTP pipeline.

Testing requires a real purchase. Create a test product priced at $0.01 or use a 100% coupon code. Place an order using a different email address than your admin account. Watch for the order confirmation email within a minute. Check that it shows your store branding and arrives in the primary inbox, not spam.

Payment gateway emails might need attention. Some gateways like PayPal or Stripe send their own notifications. These bypass your SMTP settings since they originate from the payment processor’s servers. Your WooCommerce emails still use Brevo, but payment confirmations come directly from the gateway.

Custom order status emails follow the same SMTP path. If you’ve added statuses like “Processing” or “Awaiting Payment,” those notifications use your Brevo configuration. Any email triggered by WooCommerce actions goes through your SMTP setup automatically.

Brevo SMTP Ports Explained

Brevo uses specific ports that match your security requirements – port 587 for TLS encryption, 465 for SSL, and 2525 as a backup option.

Port 587 works best for most WordPress sites. This port uses TLS (Transport Layer Security) encryption, which starts with an unencrypted connection then upgrades to secure transmission. Modern email systems prefer this approach. Gmail, Outlook, and other major providers expect traffic on port 587 for authenticated email delivery.

Port 465 handles SSL connections differently. This older standard creates an encrypted connection from the start. Some legacy systems and certain hosting environments only support port 465. While it works fine, the email industry moved toward 587 as the standard. Use 465 when your hosting specifically requires SSL or when 587 fails.

Port 2525 serves as your backup plan. Many shared hosting providers block ports 587 and 465 to prevent spam. When standard ports don’t work, 2525 often stays open. It functions identically to 587 with TLS encryption. Test this port when others fail or when your host recommends alternative SMTP ports.

Port 25 rarely works anymore. This original SMTP port lacks encryption and authentication. Most hosting providers block it completely. Internet service providers filter port 25 traffic too. Brevo supports it technically, but you’ll face delivery problems. Skip port 25 unless you have a specific technical requirement.

Hosting restrictions determine your port choice. Shared hosting plans often limit outbound connections. Check your hosting documentation or contact support to verify which ports they allow. GoDaddy, for example, blocks standard SMTP ports on basic plans. DigitalOcean and AWS require you to request SMTP access separately.

Testing different ports takes seconds. Change the port number in your SMTP plugin settings and send a test email. If it fails, try the next port. Most connection errors mention the port number in the error message. Keep trying until you find one that works with your hosting environment.

Security differences between ports stay minimal. Both 587 and 465 encrypt your email data during transmission. The technical difference involves when encryption starts, not the security level. Your emails remain protected regardless of which port you choose. Focus on finding a port that works rather than worrying about security variations.

How to Set Up Brevo SMTP in Other Apps

You set up Brevo SMTP in other applications by entering the same host, port, and API key credentials used for WordPress – the settings work universally.

Shopify needs special handling since it doesn’t allow custom SMTP configuration. Install the official Brevo app from Shopify’s app store instead. This integration syncs your store with Brevo’s system behind the scenes. Once connected, order confirmations and abandoned cart emails route through Brevo automatically. The app maps Shopify events to Brevo’s transactional templates without manual SMTP setup.

Contact form builders usually include SMTP settings. Whether you’re using Typeform, JotForm, or Google Forms with notifications, look for email or notification settings. Enter Brevo’s SMTP host, choose port 587, and use your API key as the password. Forms start delivering submissions reliably instead of using unreliable PHP mail functions.

CRM platforms like HubSpot, Pipedrive, or Zoho accept custom SMTP configuration. Navigate to email settings or integration options in your CRM. Add Brevo’s server details just like WordPress. Your CRM’s automated emails, follow-ups, and sequences now send through Brevo’s infrastructure. This improves delivery for sales emails and customer communications.

Email clients need SMTP for sending only. Outlook, Thunderbird, and Apple Mail all support custom outgoing servers. In account settings, find SMTP or outgoing mail configuration. Enter Brevo’s host and port 587. Use your Brevo username and API key for authentication. Your regular email account still receives mail normally, but sending goes through Brevo.

PHP applications require code-level changes. If you’re using PHPMailer, Symfony Mailer, or similar libraries, update the SMTP configuration in your code. Set the host to Brevo’s server, port to 587, and authentication credentials to your username and API key. Most frameworks have email configuration files where you’ll make these changes.

Mobile apps might support SMTP through their backend. If you’re building an app that sends emails, configure your server-side code with Brevo’s details. The app triggers email events, but the actual sending happens on your server using SMTP. React Native, Flutter, and native apps all work this way.

No-code tools like Zapier or Make (Integromat) connect without manual SMTP setup. These platforms have built-in Brevo integrations. Connect your Brevo account once, then create workflows that trigger emails based on various events. This approach skips SMTP configuration entirely while still using Brevo’s delivery network.

How to Test Your Brevo SMTP Setup

You test Brevo SMTP by sending a test email through your plugin or application and checking the email headers for Brevo’s server information.

Start with a basic send test from your email plugin. Every SMTP plugin includes a test feature. Enter your own email address and click send. The message should arrive within 60 seconds. If nothing shows up, check your spam folder first. Test emails sometimes trigger spam filters because they contain generic content.

Email headers tell the complete story. Open the test email and find the “View Original” or “Show Headers” option. In Gmail, click the three dots menu and select “Show original.” The headers reveal which servers handled your message. Look for references to Brevo or sendinblue (their old name) in the “Received” lines. This confirms emails route through Brevo’s servers correctly.

SPF and DKIM authentication appears in the headers too. Search for “Authentication-Results” in the header text. You’ll want to see “spf=pass” and “dkim=pass” for both authentication methods. These passes mean receiving servers trust your emails. Failed authentication leads to spam folder delivery or complete blocking.

The Brevo dashboard tracks all SMTP activity. Log into Brevo and check the Transactional or Logs section. Every email sent through SMTP appears here with delivery status. Green checkmarks mean successful delivery. Red X marks show failures. Yellow warnings indicate delays or soft bounces. Click any message for detailed delivery information.

Delivery timing matters for user experience. Send test emails at different times of day. Note how long messages take to arrive. Most should deliver within 10 seconds. Delays beyond one minute suggest configuration problems. Consistent delays might mean your IP address needs warming up or your sender reputation needs improvement.

Spam folder placement needs investigation. If test emails consistently land in spam, several factors could cause this. Your sender domain might lack proper authentication. Email content could trigger spam filters. Or your sending volume jumped too quickly. Test with different email content to isolate the issue.

Error messages provide specific clues. Connection timeouts mean port blocking. Authentication failures point to wrong API keys. “Sender not verified” means your From address isn’t approved in Brevo. Copy the exact error message and check Brevo’s documentation for specific solutions.

Real-world testing beats isolated tests. After confirming basic SMTP works, test actual site functions. Submit a contact form, reset a password, or create a test order. These real interactions sometimes reveal issues that simple tests miss. Different plugins might conflict or override SMTP settings in specific situations.

How to Fix SMTP Errors in Brevo

Most SMTP errors happen because of incorrect API keys, wrong port selection, or blocked connections from your hosting provider.

Wrong API keys cause authentication failures immediately. You’ll see errors like “Authentication failed” or “Invalid credentials” in your error logs. The fix starts in your Brevo dashboard – generate a fresh API key and copy it carefully. Replace the old key in your SMTP plugin settings. Remember, the API key goes in the password field, not a separate API field. Watch for extra spaces when pasting.

Hostname errors mean you’ve entered the wrong server address. Brevo’s SMTP server stays consistent, but typos happen. Double-check the server address matches exactly what Brevo shows in your dashboard. Some old tutorials reference “smtp.sendinblue.com” – that still works but might change. Use the current hostname from your Brevo account for future compatibility.

Firewall and hosting blocks stop connections before they start. Your error message says “Connection timeout” or “Could not connect to SMTP host.” This means your hosting provider blocks the port you’re using. Try port 2525 instead of 587. If that fails, contact your host and request SMTP ports be opened. Some hosts require upgrading to a business plan for SMTP access.

Port mismatches create confusion between encryption types. Using port 465 with TLS encryption fails because 465 expects SSL. Similarly, port 587 needs TLS, not SSL. Match your port number with the correct encryption method. When in doubt, use port 587 with TLS – it’s the modern standard.

Unverified sender addresses trigger “Sender not allowed” errors. Your From Email must exactly match an address verified in Brevo. Log into Brevo and check your Senders & Domains section. Add and verify your sender email if missing. Business domains work better than free email addresses. Gmail and Yahoo addresses often face extra restrictions.

Rate limiting kicks in after sending too many emails too quickly. Brevo applies connection and message limits, especially on free accounts. If emails suddenly stop sending after working fine, you might have hit a limit. Space out your sending or upgrade your plan. Check Brevo’s dashboard for quota warnings or usage spikes.

Step-by-step fixes work best for complex errors. First, verify your API key is current and copied correctly. Second, confirm your sender email appears in Brevo’s verified list. Third, test different ports if connections fail. Fourth, check your Brevo dashboard for account warnings or restrictions. Finally, examine actual error logs for specific messages that point to the exact problem.

Email Deliverability Tips With Brevo SMTP

You improve email deliverability by verifying your domain, warming up sending volume gradually, and maintaining clean contact lists with engaged subscribers.

Domain verification makes the biggest difference. Add your business domain to Brevo and complete SPF, DKIM, and DMARC setup. These authentication methods prove you own the domain sending emails. Without them, major email providers treat your messages suspiciously. Brevo provides exact DNS records to add – copy them perfectly into your domain settings.

SPF records tell receiving servers which IP addresses can send for your domain. Brevo gives you an SPF record that includes their servers. Add this to your domain’s DNS as a TXT record. Most domains already have an SPF record, so you’ll merge Brevo’s information into the existing entry.

DKIM adds a digital signature to every email. This signature proves the message wasn’t altered during delivery. Brevo generates unique DKIM keys for your account. Add these as TXT records in your DNS. The setup takes five minutes but dramatically improves inbox placement.

Warming up protects your sender reputation. Don’t jump from zero to thousands of emails daily. Start with 50-100 emails on day one. Double the volume every few days. This gradual increase shows email providers you’re legitimate. Sudden spikes trigger spam filters, even with perfect authentication.

Clean lists beat large lists every time. Remove email addresses that bounce repeatedly. Delete subscribers who haven’t opened emails in six months. These inactive contacts hurt your sender reputation. Email providers track engagement rates. Low opens and high bounces signal poor quality sending.

Engagement metrics guide delivery decisions. When subscribers open, click, and reply to your emails, providers notice. This positive engagement improves your reputation. Send relevant content that people actually want. Boring, irrelevant emails train spam filters to block you.

Sending frequency needs consistency. Pick a schedule and stick to it. Weekly newsletters, daily updates, or monthly summaries all work fine. Random, sporadic sending looks suspicious. Consistent patterns build trust with both subscribers and email providers.

Content quality affects technical delivery. Avoid spam trigger words, excessive capitalization, and too many exclamation points. Balance text with images. Include a clear unsubscribe link. These factors seem minor but influence whether emails reach the inbox or spam folder.

FAQs