← Back to Blog
Mautic Migration Marketing Automation

Mautic with Amazon SES: dedicated IP and how to plan the warm-up

Mautic with Amazon SES: shared vs dedicated IP, standard vs managed warm-up, and why warm-up starts after cutover. Lessons from a Marketo migration.

M Mautomic Team
7 min read

Amazon SES is a common way to send email from Mautic. It is cheap and reliable. The hard part is the IP address: shared or dedicated, standard or managed, and when the warm-up really happens. Below is how we set it up when moving a German B2B distributor from Marketo to Mautic, with SES in Frankfurt and a dedicated IP.

Why use Amazon SES with Mautic?

Mautic does not send email itself. It hands messages to a transport, and SES is one of the most popular choices. You pay per message, the service scales to millions of emails, and you can pick an EU region for your data.

Our client sends a large newsletter once a week. Automated shop emails add a steady trickle every day.

Shared or dedicated IP?

By default, SES sends your email from IP addresses shared with other SES customers. AWS manages their reputation. A dedicated IP is yours alone: your reputation, good or bad, depends only on how you send.

AWS is clear about when a dedicated IP makes sense. From the SES documentation: “If you don’t plan to send large volumes of email on a regular and predictable basis, we recommend that you use shared IP addresses.”

The key words are regular and predictable. Volume alone is not enough. A team that sends 50,000 newsletters once a week and very little in between does not have a regular pattern. Mailbox providers build reputation from consistent sending. Long quiet periods followed by a spike do not help.

For managed dedicated IPs AWS also names a lower bound. From the managed dedicated IP documentation: “If you send small volumes of email (less than a few hundred per day over a few days), it would be more beneficial to send through the SES shared IP pool.”

Our client sits between the two cases. The newsletter goes out about once a week, so the pattern is regular. Each send is a large batch followed by quiet days. A managed dedicated IP copes with that better than a standard one, and the setup works well today. We watch deliverability after every newsletter and will move the client to shared IPs if the numbers call for it.

We ask about the sending pattern in the first call, before anyone orders a dedicated IP.

Standard or managed dedicated IP?

SES offers two kinds of dedicated IP. The difference matters most for the warm-up.

StandardManaged
SetupRequest via AWS SupportOpt in, SES allocates the IPs
Warm-upAutomatic by default, time-based, 45 daysAutomatic, adaptive, per mailbox provider
Depends on your sending volume?No, the percentage grows with timeYes, it follows your real sending
Number of IPsFixed, you add or remove themScales with your volume
Known, unchanging IP addressesYesNo
Irregular sending patternsNot recommendedRecommended over standard

A few details from the warm-up documentation:

  • Standard IPs warm up on a timer. During the first 45 days, SES splits your sending between your new IP and the shared pool, and shifts the share toward your IP over time. The percentage grows “independently from your sending volume”. You can switch the automatic warm-up off and run it yourself.
  • Managed IPs warm up by usage. SES uses an adaptive strategy, together with the shared pool, that follows your actual sending to each mailbox provider. It also adds IPs when your volume grows.

A common assumption is that only managed IPs warm up automatically. Both do, in different ways. Check the current AWS docs before you promise anyone a warm-up schedule.

In this project we use a managed dedicated IP. SES mixes it with the shared pool and decides the split itself, based on real sending to each mailbox provider. There is no fixed calendar. An IP that is already warm for Gmail can still be cold for Outlook or GMX.

Why the warm-up starts after the cutover

It is tempting to run the IP warm-up in parallel with the build. On paper that looks efficient: the IP would be warm on go-live day.

In practice, the warm-up needs real email. Real email only starts flowing when the client sends from the new platform, and that happens after the cutover. During the build there is nothing to send except tests. With a managed IP, which follows actual sending, the warm-up simply cannot happen in advance.

Starting earlier would mean moving part of the live newsletter to the new platform before the cutover. That needs two synchronised contact lists and a guard against duplicate emails. It can work when the build starts well ahead of the deadline and the newsletter moves first. On a two-month project the cleaner choice is a warm-up right after go-live.

What we tell clients:

  • The warm-up belongs to the first weeks after go-live, not to the build phase.
  • Expect four to six weeks before the dedicated IP carries the full volume. AWS says reputation can take from about two weeks to six weeks, depending on the mailbox provider.
  • During that time part of your mail still goes through shared IPs. That is normal and it is not a problem.

Sending in waves while the IP warms up

Even with an automatic warm-up, the first big newsletter should not go to everyone at once. We split the client’s audience into waves that grew with each send.

Good practice during the warm-up:

  1. Start with your most engaged contacts: recent openers, recent buyers.
  2. Grow the volume step by step. Do not double it overnight.
  3. Watch bounces and complaints after each wave. Slow down if blocking or throttling notices appear.
  4. Send something every day if you can. Daily automated emails help the warm-up more than one weekly spike.

Watch the account limits too. In this project the SES account in Frankfurt (eu-central-1) allowed 50,000 emails a day and 14 per second, the default values shown in the SES dashboard. These limits belong to the account, not to the IP. We set the Mautic cron to broadcasts:send --limit=520 every 15 minutes, which keeps a full day just under 50,000.

How do bounces and complaints get back to Mautic?

SES knows when an email bounces or a recipient marks it as spam. Mautic needs to know too, so it stops sending to that address.

The setup:

  • SES publishes hard bounce and complaint notifications to Amazon SNS.
  • SNS calls a Mautic webhook, provided by the matbcvo/mautic-amazon-sns-callback plugin.
  • Mautic marks the contact as Do Not Contact with the reason: bounced, or unsubscribed after a complaint.

Protect the webhook. Ours sits behind a path that nobody can guess. We looked at an allowlist of AWS IP ranges and rejected it: the ranges carry no SNS tag, so the list would let in any EC2 machine in the region, and it would break silently when AWS rotates the ranges. The strongest protection is verifying the signature of each SNS message, so check whether your callback plugin supports it.

Test the whole chain before the first real send. SES has a mailbox simulator with addresses that trigger each case:

AddressWhat SES doesWhat Mautic should do
success@simulator.amazonses.comDeliversNothing
bounce@simulator.amazonses.comHard bounce, “550 5.1.1 Unknown User”Do Not Contact, bounced
ooto@simulator.amazonses.comDelivers, returns an out-of-office replyNothing
complaint@simulator.amazonses.comRecipient marks the email as spamDo Not Contact, unsubscribed
suppressionlist@simulator.amazonses.comHard bounce, as for an address on the SES suppression listDo Not Contact, bounced

This replaced a Marketo program that categorized bounces by hand. One automation less to maintain.

DNS: SPF, DKIM, DMARC and who applies them

Your sending domain needs SPF, DKIM and DMARC records before the first real send. Writing the records is easy. Getting them applied often is not.

In this project the client’s IT managed DNS. We sent the records with an instruction sheet, and they were in place almost three weeks later, in the middle of the summer holidays. Plan two to three weeks for DNS, and ask for the DNS owner’s name in the first call.

Also agree on two different domains early:

  • The sending domain, for example mail.example.com. It only needs DNS records, it does not point to a server.
  • The Mautic domain, which serves the admin panel, landing pages and forms. It points to your Mautic server. Marketo users find this new: in Marketo the app lives on Adobe’s domain and only landing pages sit on yours.

A checklist before you order a dedicated IP

  • How many emails do you send per month, and how are they spread across the week?
  • Is the volume regular and predictable? If not, consider shared IPs or a managed dedicated IP.
  • Whose AWS account will SES run in, yours or your agency’s?
  • Which region? For EU data, Frankfurt or Ireland.
  • Who owns DNS, and how fast can they apply records?
  • Is the warm-up planned for the weeks after go-live?
  • Is the first big send split into waves, starting with engaged contacts?
  • Are bounce and complaint notifications wired to Mautic and tested with the SES mailbox simulator?
  • Did you export deliverability metrics from the old platform, so you can compare later?

The last point is easy to forget. When the old contract ends, its statistics go with it, and so does your baseline for bounce rate and inbox placement. Export them while you still have access.

Moving to Mautic and not sure about the sending setup?

This is one of the building blocks of our Marketo to Mautic migration for Meesenburg.

Tell us your volume and sending pattern. We will recommend shared or dedicated IPs and plan a warm-up that fits your calendar. See our Mautic support and maintenance.

Tags

#Mautic#Amazon SES#Deliverability#IP warm-up#Marketo
M

Written by

Mautomic Team

Mautic experts sharing insights on marketing automation, custom development, and open-source technology.

Need help with Mautic?

Our team of experts is ready to help you implement and optimize your marketing automation.

We'll get back within 24h. Privacy Policy