External SMTP Relay – Brevo, SendGrid, Mailgun for Reliable Delivery

Mail sent directly from your hosting server often lands in spam — even when configured correctly. Shared hosting IPs have variable reputation; major providers (Gmail, Outlook) filter aggressively. The reliable fix is routing your outbound mail through a dedicated transactional email service like Brevo, SendGrid, Mailgun, or Postmark. Their IPs are warmed-up, monitored, and trusted. This guide covers when relay makes sense, picking a provider, and the actual setup.

When to use external SMTP relay

• Mail keeps landing in spam folders. Especially Gmail and Outlook.com.
• Bulk transactional mail. Order confirmations, password resets, notifications — volume matters.
• Server reputation is poor. Shared IP with bad neighbors.
• Compliance/audit requires deliverability tracking. Need to prove mail was delivered.
• Port 25 is blocked. Some hosting providers (including some iWebVault servers like cobra/asura) block port 25 for security. SMTP relay via port 587 bypasses this.

When you probably don’t need relay

• Low-volume personal email.
• Your hosting IP is already good and delivers reliably.
• You’re sending to a small group of recipients who never report you.

Popular providers compared

For iWebVault customers, Brevo and SendGrid are common choices because free tiers cover most small business needs.

Setup overview

All providers follow same pattern:

1. Sign up with provider.
2. Verify your domain (add DNS records they provide — SPF, DKIM).
3. Get SMTP credentials (host, port, username, password) or API key.
4. Configure your application (WordPress, PHP, etc.) to send via their SMTP.
5. Test delivery.

Brevo SMTP setup with WordPress

Step 1: Brevo account

1. Sign up at brevo.com.
2. Verify your email.
3. Add your sending domain (yourdomain.com).
4. Brevo provides DNS records: SPF and DKIM TXT entries. Add to your iWebVault DNS zone (cPanel → Zone Editor).
5. Brevo verifies domain after DNS propagates.

Step 2: Get SMTP credentials

1. Brevo → SMTP & API → SMTP.
2. Generate SMTP key. Note these values:

• Host: smtp-relay.brevo.com
• Port: 587
• Login: your Brevo account email
• Password: the generated SMTP key

Step 3: WordPress configuration

1. Install plugin “WP Mail SMTP.”
2. Settings → WP Mail SMTP.
3. From Email: your domain email (e.g. noreply@yourdomain.com).
4. From Name: your site name.
5. Mailer: select “Other SMTP.”
6. SMTP Host: smtp-relay.brevo.com
7. Encryption: TLS
8. SMTP Port: 587
9. Authentication: ON
10. SMTP Username: your Brevo login email
11. SMTP Password: your Brevo SMTP key
12. Save.
13. Test Email tab → send test → verify received.

WordPress now routes ALL outbound mail through Brevo. Better deliverability immediately.

SendGrid setup with WordPress

Same pattern:

1. Sign up at sendgrid.com.
2. Settings → Sender Authentication → Authenticate Your Domain. Add DNS records.
3. Settings → API Keys → Create API Key. Choose “Full Access” or restricted to Mail Send.
4. WP Mail SMTP → Mailer: SendGrid. Paste API key.
5. Save. Test.

SendGrid plugin uses API directly (not SMTP), which can be more reliable than SMTP path.

Setup from PHP (non-WordPress)

If you’re sending from custom PHP, use PHPMailer with SMTP:

require 'vendor/autoload.php';

use PHPMailerPHPMailerPHPMailer;

$mail = new PHPMailer(true);
$mail->isSMTP();
$mail->Host = 'smtp-relay.brevo.com';
$mail->SMTPAuth = true;
$mail->Username = 'your-email@yourdomain.com';
$mail->Password = 'your-brevo-smtp-key';
$mail->SMTPSecure = 'tls';
$mail->Port = 587;

$mail->setFrom('noreply@yourdomain.com', 'Your Name');
$mail->addAddress('recipient@example.com');
$mail->Subject = 'Test';
$mail->Body = 'Hello!';
$mail->send();

Install via Composer: composer require phpmailer/phpmailer.

DNS records you must add

Every relay provider requires DNS verification of your sending domain. Typically:

• SPF record — Authorizes the relay’s IPs to send for your domain.
• DKIM records — Public keys for signature verification. Usually 2-3 CNAME records.
• Sometimes DMARC — Reporting/policy directive.

Provider gives you exact records to add. cPanel → Zone Editor → add as TXT or CNAME as specified. Wait for propagation (minutes to hours). Verify in provider’s dashboard.

Without these records, mail delivers but is treated suspiciously.

Verifying relay is active

• Send test message to your Gmail.
• Open the email in Gmail → 3-dot menu → Show original.
• Look at “Received” headers. Should show smtp.brevo.com or sendgrid.net as last hop.
• SPF, DKIM, DMARC results — all should pass.
• Provider dashboard shows the sent message in delivery log.

Common issues

“Authentication failed (535).” Wrong username or password. SMTP key is different from your account password.

“Mail delivered but to spam.” SPF or DKIM not configured properly. Verify DNS records exist and propagated. Use mail-tester.com to check.

“Mail accepted by relay but recipient says nothing arrived.” Provider dashboard shows delivery status. Often “blocked” or “bounced” with reason. Recipient’s server may be rejecting based on your sender reputation history.

“Hit free tier limit.” Provider stops sending until next period. Upgrade plan or wait.

“Sender address rejected — not verified.” Provider requires the From address’s domain to be verified. Complete DNS authentication.

Pricing realistic guidance

• Under 100 transactional emails/day — Free tiers sufficient.
• 100-300 emails/day — Brevo free tier still covers.
• 1,000-10,000 emails/day — Cheapest paid plan from most providers.
• Marketing campaigns / newsletters — Different pricing model; use dedicated newsletter service (Mailchimp, ConvertKit, Brevo marketing).

Common questions

“Does using SMTP relay affect inbound email?” No. Relay handles outbound only. Inbound still goes to iWebVault mail server.

“Why does iWebVault mail land in spam without relay?” Shared hosting IPs have variable reputation. Dedicated relays maintain perfect reputation as core business.

“Can I send 50,000 emails to a mailing list via SMTP relay?” Yes, but you’ll hit rate limits and rules around list management. Use the relay’s bulk marketing tool rather than firing 50k SMTP messages from your server.

“My port 25 is blocked. Can I still use SMTP relay?” Yes — relays use port 587 (submission) or 465. Both typically unblocked.

“What if relay goes down?” Outbound mail queues then fails. Configure fallback in WP Mail SMTP — secondary relay.

What’s next

• SPF/DKIM/DMARC: Email authentication.
• SMTP from PHP and apps: SMTP from apps.
• Email troubleshooting: Mail queue.

External SMTP relay is the single biggest improvement available for email deliverability on shared hosting. Setup takes 30 minutes; the result is mail consistently landing in inboxes, not spam folders. For any site that genuinely depends on transactional email — order confirmations, password resets, notifications — it’s the right choice. Brevo’s free tier handles most small business needs without ever requiring payment.