Skip to content
Get a quote

Client work · Email sending infrastructure

Amazon SES and Mautic: Email Sending Setup

Virtus Development, a software development company, wanted to send its own email through Amazon SES. We took the account out of the SES sandbox with a production access request, verified the sending identities and set up SPF, DKIM and DMARC, wrote a restricted IAM policy for sending from code, connected bounce and complaint notifications through SNS, and installed self-hosted Mautic with a warm-up guide, followed by a week of support.

The problem

What needed solving

A new Amazon SES account starts in a sandbox: it can only send to verified addresses, in small amounts. To send real email, the account owner has to ask Amazon for production access and show that bounces and complaints will be handled. Until then, SES is a test bench.

The client also wanted its own marketing platform rather than a hosted one, so that contacts and campaigns stay on its servers. That meant installing Mautic, pointing it at SES, and warming up the new sending reputation slowly instead of sending everything on day one.

Constraints

What the build had to respect

  • Amazon reviews the request

    Production access is granted by Amazon after a request that explains how the account will send and how it handles bounces and complaints.

  • Least privilege

    Code that sends email should hold only the permission to send. The IAM policy was written for that job, not as a general admin key.

  • Domain authentication

    Mail providers trust a domain that proves its sender with SPF, DKIM and DMARC records, so those DNS records were part of the setup, not an afterthought.

  • A new reputation

    A new sender has no history, so volume has to grow gradually. The warm-up guide sets out how.

What we built

The build, part by part

Six pieces of work, each named in the order.

Amazon SES

  • Removal of the sandbox restrictions through production approval
  • Identity verification for the sending domain

Authentication

  • SPF, DKIM and DMARC records in DNS

Access

  • An IAM policy for sending from code, and nothing more

Feedback loop

  • Bounce and complaint notifications through Amazon SNS webhooks

Mautic

  • A self-hosted Mautic marketing platform, deployed and connected to SES
  • A warm-up guide for the new sender

Support

  • A week of support after handover
How an email leaves and what comes back
  1. Mautic or app code

    Creates the email

  2. IAM policy

    Allows sending only

  3. Amazon SES

    Signs and sends

  4. Mailbox provider

    Checks SPF, DKIM, DMARC

  5. SNS notification

    Bounces and complaints

  6. Contact updated

    Bad addresses stop

Stack and integrations

Amazon Web Services
  • Amazon SES
  • Amazon SNS
  • AWS IAM
Marketing platform
  • Mautic (self-hosted)
DNS
  • SPF
  • DKIM
  • DMARC

Screens

What it looks like

Screenshots from the project. Browser bars are cropped, and people's details, prices and the client's own figures are covered.

  • Both sending identities verified in Amazon SES.
  • The account out of the sandbox, with healthy status. Quotas are covered.

Handover

Records behind this page

We do not hold the build files for this project, so this page is written from the order record and the scope agreed in it.

  • A Fiverr order, February 2025
  • The scope listed above, as agreed in the order, including the week of support
  • The client's own review, quoted below exactly as written

Status and link

Where it stands

Delivered in February 2025. The sending setup runs in the client's own AWS account, so there is nothing public to link.

In the client's words

What the client wrote

Working with Shohrab H. was an absolute pleasure! His incredible PROFESSIONALISM and attention to detail in email marketing were top-notch. Plus, his quick responsiveness and superb cooperation made the entire experience seamless. Highly RECOMMEND! 🙌

V., Fiverr order. Verbatim Fiverr review, unedited. Read it on Fiverr (opens in a new tab)

What we leave out

What we do not claim

No sending volumes, inbox placement rates or deliverability scores: we have none on record. Production access is Amazon's decision; our part was a request and a setup that meet its rules.

Next step

Need something like this?

Tell us what you have today and what should change. We reply within one business day. You get a written scope and a fixed quote before anything is built.