The Engineer's Guide: How to Setup Your Own SMTP Infrastructure

At a certain scale, paying a third-party marketing platform thousands of dollars a month just to push data around becomes a severe liability. If you have a database of 200,000 users, relying entirely on a consumer-grade drag-and-drop tool is an architectural mistake.

When you understand how email actually works, you realize that most popular marketing platforms are simply charging you a massive premium for a graphical user interface (GUI). Underneath that GUI, they are just routing your text through an SMTP server.

Today, we are cutting out the middleman. We are going to break down exactly how to set up your own SMTP infrastructure. We will cover the difference between bare-metal routing and managed relays, and I will show you how to configure the DNS records required to ensure Google and Yahoo actually let you into the primary inbox.

1. Bare-Metal vs. Managed Relays

When engineers decide to "host their own email," they usually make a critical, painful mistake: they try to spin up a bare-metal Postfix server on a DigitalOcean droplet. Do not do this.

Sending an email is incredibly easy. Getting an email delivered is brutally difficult. If you run your own Postfix server from a raw IP address, you will immediately be blacklisted by Spamhaus, Google, and Microsoft. Building IP reputation from scratch takes years of flawless sending.

The smart solution is the Managed SMTP Relay.

Instead of managing your own sender reputation, you use a headless routing engine. You bring your own frontend (like Sendy, Mautic, or a custom Next.js dashboard), and you pass the emails to a secure, highly-reputable managed API.

2. The Holy Trinity of Deliverability (SPF, DKIM, DMARC)

If you use a managed relay, your only real job is proving to the internet that you own the domain you are sending from. In 2026, Google requires strict adherence to three DNS protocols. If you miss even one, your emails will bounce.

3. The Concept of IP Warming

Once your DNS is configured, you cannot immediately blast 100,000 emails. If a previously quiet domain suddenly sends 100,000 emails in an hour, Google’s automated threat algorithms will instantly assume you are a hacked domain and blacklist you.

You must perform IP Warming. This is the process of gradually increasing your sending volume over 30 days to prove to inbox providers that your traffic is legitimate and that users are actually opening your content.

• Week 1: Send 50 - 100 emails per day (Only to your most engaged users).
• Week 2: Send 500 - 1,000 emails per day.
• Week 3: Send 5,000 - 10,000 emails per day.

4. Choosing Your Infrastructure Partner

If you are building an application or hosting your own frontend marketing engine (like Sendy), you need an SMTP relay that is fast, secure, and has impeccable shared IP reputation.

While AWS SES is notoriously cheap, getting approved for production access is a nightmare. Amazon routinely rejects applications because they are terrified of spammers ruining their IPs. Furthermore, their dashboard is notoriously hostile to non-DevOps engineers.

For 90% of use cases, I strictly deploy Brevo's SMTP API.

Because Brevo started natively as a transactional email engine (before expanding into a marketing platform), their core routing infrastructure is enterprise-grade. They provide you with the exact DNS values to copy-paste into Cloudflare, they automatically handle IP warming if you upgrade to a dedicated IP, and their webhooks allow you to track bounces programmatically in real-time.