This project aims to simplify the integration with AWS Simple Email Service (SES) by providing a REST API for managing SES configurations, email templating, sending, and scheduling.

The project consists of two main components:

• REST API: Handles domain identity registration, email template creation and management, as well as immediate or scheduled email sending.
• Event Processor: A background service responsible for processing scheduled emails, handling retries, and managing domain validation.

This solution streamlines email operations with AWS SES, reducing complexity and improving efficiency.

EzMail aims to be an open-source, self-hosted alternative to Resend. It is not affiliated with, endorsed by, or associated with Resend in any way.

make build-api

This will create a binary in folder dist/api called ezmail

make build-executor

This will create a binary in folder dist/executor called executor

Info: Both RESCHEDULE_RETRIES and RESCHEDULE_TIME_MS must be set to enable email retrying

To be able to run the api and the executor you will require a MySQL database and a Redis instance.

• The MySQL database is used to store the required domain information, templates and emails.
• The Redis instance is used both as a event queue and to schedule future events, as for example scheduling an email for later.

Important: The running environment will also require AWS permissions to be able to use the SES service.

If AUTH_TOKEN env variable is defined then all requests require an Authorization header with a Bearer token:

Authorization: Bearer YOUR_ACCESS_TOKEN

• You can find a full api definiton under .dev/api.http

Request Body:

{
    "name": "domain.tld",
    "region": "eu-west-1"
}

Request Body:

{
    "html": "<div>Hello [[FIRST_NAME]]</div>",
    "text": "Hello [[FIRST_NAME]]",
    "subject": "Salutations from [[COMPANY_NAME]]"
}

Request Body:

{
    "from": "Name <source@domain.tld>"
    "to": [ "user@example.com" ],
    "template_id": "TEMPLATE_ID",
    "context": {
        "FIRST_NAME": "John",
        "COMPANY_NAME": "Acme Inc."
    },
    "reply_to": "email_to_reply@domain.com",
    "bcc": [ "bcc_email@somedomain.tld" ],
    "when": "2024/10/12 20:37:00"
}

Email fields follow the RFC 5322 format and can include a display-name. Example:

• name@domain.com : email without a display-name
• Name Surname <name@domain.com> : email with a display-name

bcc, reply_to and when fields are optional

Using the when field you can schedule an email for later, dates are UTC

• Build both binaries
• Start the required services (MySQL and Redis)
• (Only once) Setup MySQL db schema (you can find it in .dev folder)
• Run both binaries (setup env variables first)
• Call the api to register your domain
  • The domain registration will return a list of DNS records you should create in order to start using the domain in AWS SES
  • Wait for the domain to get validated (you can manually trigger the status refresh using the designated endpoint)
• Once the domain is validated you can start sending emails, first step would be to create a template and next you should be able to send an email*

* Keep in mind that once the domain is validated you will still need to request production access(disable sandbox) in your AWS console.

• Go to docker folder
• Copy .env.example to .env and configure it as you wish
• Check docker-compose.yml for extra config, for example on how AWS credentials are shared with the docker instances
• Run:

docker compose up -d

• Continue with domain registration and validation as explained in the How to use it? section