Other providers & SMTP

Amazon SES is our recommended provider, but EmailFlow AI connects to every major sending vendor and to any standard SMTP relay. Pick whichever fits your traffic, budget, and existing DNS setup — the connection process is the same: add a server, paste credentials, send a test.

SendGrid

SendGrid offers both a Web API and SMTP. For the API driver, create a SendGrid API key with Mail Send permission and paste it into the SendGrid (API) server. For SMTP, use host smtp.sendgrid.net, port 587, username apikey, and your API key as the password. Verify your domain in SendGrid and publish its DKIM records so mail is signed as you.

Mailgun

Mailgun is popular with developers and provides an HTTP API and SMTP. For the API driver, supply your Mailgun domain and API key, and choose the correct region (US or EU) — Mailgun keys are region-specific. For SMTP, use the SMTP credentials Mailgun generates for your domain. Add and verify your domain in Mailgun before sending.

Elastic Email

Elastic Email is a cost-effective choice for bulk sending. Create an API key in your Elastic Email account and add it to the Elastic Email (API) server, or use the provided SMTP credentials. As always, verify your sending domain on the provider side and authenticate it in EmailFlow AI for DKIM.

SparkPost

SparkPost provides an analytics-rich transactional API. Generate an API key with transmission permissions and paste it into the SparkPost (API) server, choosing the US or EU host to match your account. SMTP is also supported with SparkPost's SMTP credentials.

Blastengine

Blastengine is a Japanese transactional email service. Enter your Blastengine login ID and API key in the Blastengine (API) server, or use SMTP credentials if you prefer. This is a good option if your audience and infrastructure are based in Japan.

Generic SMTP

Have your own SMTP server, a corporate relay, or a provider not listed above? Choose Generic SMTP and enter the host, port (usually 587 for STARTTLS or 465 for TLS), encryption mode, username, and password. Any RFC-compliant SMTP server works. This is the universal fallback — if a vendor gives you SMTP credentials, you can connect it.

lan

Whatever provider you choose, the rest of the pipeline is identical: authenticate your sending domain (DKIM), add a tracking domain, and send. You can connect several providers and route across them.

Choosing between API and SMTP

Most providers offer both. The API driver typically returns richer delivery, bounce, and complaint signal and is slightly faster to authenticate. SMTP is universal and a safe choice if you already have working SMTP credentials. Either way your recipients receive identical mail; you can switch later without rebuilding campaigns.

Frequently asked questions

Do I still need to verify my domain with each provider? Yes. Each provider verifies sending identities independently, so publish the DKIM/SPF records it gives you, then authenticate the same domain in EmailFlow AI.

Can I migrate from one provider to another? Absolutely — add the new server, test it, make it primary, and remove the old one. Your campaigns, lists, and automations are unaffected.

Is any provider metered by EmailFlow AI? No. Sending volume is unlimited on every plan regardless of provider; you pay your provider directly.