Home » Email Deliverability » SMTP Setup

How to Configure SMTP for Bulk Email Sending

Configuring SMTP for bulk email means connecting your email platform to a dedicated email delivery service (like SendGrid, Mailgun, or Amazon SES) using SMTP credentials. You need the SMTP host, port, username, and password from your provider. Most platforms accept these settings in a straightforward configuration form, and once connected, your emails are sent through the provider's infrastructure with proper authentication and deliverability features built in.

What Is SMTP and Why You Need a Dedicated Provider

SMTP (Simple Mail Transfer Protocol) is the standard protocol for sending email across the internet. Every email you send uses SMTP, even if you never see the settings. When you send from Gmail or Outlook, your email client connects to Google's or Microsoft's SMTP servers behind the scenes.

For bulk email marketing, you cannot use your regular business email account's SMTP. Gmail limits you to 500 emails per day (2,000 with Workspace), and sending bulk marketing through a personal account will get it suspended. You need a dedicated email delivery service that is built for high-volume sending, with features like deliverability monitoring, bounce handling, webhook callbacks, and ISP relationship management.

Choosing Your SMTP Provider

The major email delivery providers for bulk sending are:

SendGrid: Widely used, good documentation, free tier of 100 emails/day. Offers both SMTP relay and a web API. Owned by Twilio.
Mailgun: Developer-friendly, strong API, good deliverability tools. Free trial includes 5,000 emails. Owned by Sinch.
Amazon SES: Cheapest at high volume ($0.10 per 1,000 emails), but requires more manual setup and monitoring. Good choice if you are already on AWS.
Elastic Email: Budget-friendly with a generous free tier. Good for smaller senders getting started.
Postmark: Premium deliverability focus, best for transactional email. Higher cost but excellent inbox placement.

See the detailed provider comparison for pricing, features, and which is best for your use case.

How to Get Your SMTP Credentials

Step 1: Create an account with your chosen provider.
Sign up at the provider's website. Most have free tiers or trials so you can test before committing.

Step 2: Verify your sending domain.
Before you can send, the provider requires you to prove you own the domain. This involves adding DNS records. See the domain verification guide for detailed steps.

Step 3: Generate SMTP credentials.
In your provider's dashboard, find the SMTP settings. The provider gives you four values: SMTP host (e.g. smtp.sendgrid.net), port (typically 587 for TLS or 465 for SSL), username (often "apikey" for SendGrid or your account email for Mailgun), and password (usually an API key, not your account password).

Step 4: Enter the credentials in your email platform.
In the Email Broadcast app settings, enter the SMTP host, port, username, and password. Set the From email address to an address on your verified domain. Set the From name to your brand name or sender name.

Step 5: Send a test email.
Send a single test email to your own address. Check that it arrives, that the From address is correct, and that the email headers show spf=pass and dkim=pass. If the test fails, double-check your credentials and make sure port 587 or 465 is not blocked by your hosting firewall.

SMTP Ports Explained

Port 587 (recommended) - SMTP with STARTTLS encryption. The connection starts unencrypted and upgrades to TLS. This is the standard port for email submission and works with almost all providers.
Port 465 - SMTP over implicit SSL/TLS. The connection is encrypted from the start. Some providers support this as an alternative.
Port 25 - The original SMTP port for server-to-server email relay. Most cloud hosting providers (AWS, Google Cloud, Azure) block outbound port 25 to prevent spam. Do not use port 25 for client submission.
Port 2525 - An unofficial alternative that some providers offer when 587 and 465 are blocked. SendGrid and Mailgun both support it.

Using Multiple SMTP Providers

For higher volume senders, using multiple SMTP providers improves deliverability and provides redundancy. If one provider has an IP reputation issue or an outage, your other providers continue sending normally. The ISP volume shaping guide covers how to distribute sends across providers for optimal inbox placement.

The Email Broadcast app supports configuring multiple SMTP providers and can distribute sends across them. This is especially valuable at higher volumes where you want to avoid putting all your sending through a single IP range.

Common SMTP Configuration Mistakes

Using your account password instead of an API key. Most providers use API keys as the SMTP password, not your login password.
Wrong port. Try 587 first. If that does not work, try 465 or 2525.
Firewall blocking outbound connections. Some hosting providers block SMTP ports by default. You may need to open a support ticket to allow outbound SMTP.
From address not on verified domain. If you try to send from an unverified domain, the provider will reject the message.

After setup: Do not immediately send to your entire list. Start with a small batch of engaged subscribers and gradually increase volume over 2-4 weeks. This builds your sending reputation with ISPs. See the IP warming guide for a detailed schedule.

Configure your email sending infrastructure with support for multiple SMTP providers, automatic ISP volume shaping, and deliverability monitoring.

Get Started Free

View the Email Broadcast App