# Email Delivery Connections

> Mailrith is provider-agnostic — you connect your own email delivery service and Mailrith handles campaign logic, subscriber targeting, and engagement tracking on top of it.

- Human page: https://mailrith.com/docs/email-delivery-connections
- Category: Campaigns & Delivery
- Reading time: 12 min read

## What this guide covers
Connect your email sending provider, configure sender identity, test delivery, and set up webhooks for bounce and complaint tracking.

## Sections
- Supported Providers
- Provider Setup Guides
- Create and Test a Connection
- Webhooks
- Using Connections in Sends

## Visual Reference
![Mailrith email delivery connections page showing connected providers with action controls.](https://mailrith.com/docs/screenshots/email-delivery-connections.png)

Each connection stores the sender identity, provider credentials, workspace assignments, and webhook endpoints. Use the test email action to verify everything works before going live.

## Supported Providers

Mailrith manages subscribers, targeting, campaign content, automations, and reporting. Your email delivery provider sends the actual email. This gives you control over your sender reputation and lets you use the provider that already fits your business.

A delivery connection stores the provider credentials, sender identity, webhook settings, and the workspaces that are allowed to use that sender. You need at least one enabled connection before broadcasts, sequences, and automation email steps can send to real subscribers.

Mailrith supports these provider types:

- [Amazon SES](https://mailrith.com/docs/setup-amazon-ses.md): useful when your team already uses AWS and wants regional control, verified identities, and SNS-based delivery events.
- [Postmark](https://mailrith.com/docs/setup-postmark.md): useful when you want a focused sending service with server tokens, message streams, and clear delivery events.
- [SendGrid](https://mailrith.com/docs/setup-sendgrid.md): useful when your team already uses SendGrid API keys and Event Webhooks.
- [Mailgun](https://mailrith.com/docs/setup-mailgun.md): useful when you send from a verified Mailgun domain and need to choose the correct US or EU region.
- [Resend](https://mailrith.com/docs/setup-resend.md): useful for straightforward API-based sending with verified domains.
- [Brevo](https://mailrith.com/docs/setup-brevo.md): useful when your sender identity and transactional email setup already live in Brevo.
- [Custom SMTP](https://mailrith.com/docs/setup-custom-smtp.md): useful for other SMTP servers or corporate mail relays that support standard SMTP login details.

You can create more than one connection. For example, one workspace can use a newsletter sender while another uses a client-specific sender, or one team can keep a test sender separate from the sender used for production campaigns.

If the sender setup terms are unclear, read [SMTP, APIs, and Delivery Providers](https://mailrith.com/guides/smtp-and-delivery-providers.md), [Email Types and Sender Separation](https://mailrith.com/guides/email-types-and-sender-separation.md), and [Sender Domains and Email Authentication](https://mailrith.com/guides/sender-domains-and-authentication.md) before choosing a connection.

## Provider Setup Guides

Each provider has its own setup steps because each provider names credentials and webhooks differently. Use the guide for your provider before creating the connection:

- [Set Up Amazon SES](https://mailrith.com/docs/setup-amazon-ses.md) for AWS region, access key, secret key, verified identity, and SNS events.
- [Set Up Postmark](https://mailrith.com/docs/setup-postmark.md) for server token, optional message stream, and Postmark webhooks.
- [Set Up SendGrid](https://mailrith.com/docs/setup-sendgrid.md) for API key, sender authentication, and Event Webhook setup.
- [Set Up Mailgun](https://mailrith.com/docs/setup-mailgun.md) for API key, sending domain, region, and webhook routing.
- [Set Up Resend](https://mailrith.com/docs/setup-resend.md) for API key, verified domain, and webhook setup.
- [Set Up Brevo](https://mailrith.com/docs/setup-brevo.md) for API key, verified sender, and webhook setup.
- [Set Up Custom SMTP](https://mailrith.com/docs/setup-custom-smtp.md) for host, port, security mode, username, password, and optional event forwarding.

If you are not sure which provider to choose, start with the one your domain is already verified in. Changing providers later is possible, but sender reputation and authentication work are usually easier when you continue from an existing verified setup.

## Create and Test a Connection

1. Click **Email Delivery Connections** in the left sidebar.
2. Click **Create Connection** in the page header.
3. In the **Select Email Delivery Service** drawer, select the provider you already prepared, such as **Amazon SES**, **Postmark**, **SendGrid**, **Mailgun**, **Resend**, **Brevo**, or **Custom SMTP**.
4. In the **Connect Email Delivery Service** drawer, enter a clear **Connection Name** that tells teammates what the sender is for.
5. Enter the **From Name** and **From Email** subscribers will see.
6. Use **Workspaces** to assign the connection only to the workspaces allowed to send from this identity.
7. Fill the provider credential fields shown for that provider, such as **API Key**, **Server API Token**, **Region**, **Access Key ID**, **Secret Access Key**, **Sending Key**, **Sending Domain**, **SMTP Host**, **Port**, **Security**, **Username**, or **Password**.
8. Click **Save**.
9. In the connection row, click **Send Test Email** before using the connection in a real broadcast, sequence, or automation.

- **Connection name:** an internal label such as "Main Newsletter SES" or "Client A Postmark". Subscribers do not see this name.
- **From name:** the sender name subscribers see in their inbox, such as "Acme Updates".
- **From email:** the sender email subscribers see. This address or its domain must be approved by the provider.
- **Provider credentials:** the API key, token, AWS key, SMTP details, or other secret needed to send through the provider.
- **Workspace assignment:** the workspaces that can use this connection. A connection assigned to the wrong workspace will not appear where you expect it.

After saving, send a test email before using the connection in a real campaign. The test checks the most important parts of setup: whether Mailrith can authenticate with the provider, whether the sender identity is allowed, and whether the message reaches an inbox.

A successful test send does not always prove authentication is aligned. If you are preparing a real sender domain, use [From, Reply-To, and Return-Path](https://mailrith.com/guides/from-reply-to-and-return-path.md) and [DMARC Alignment](https://mailrith.com/guides/dmarc-alignment.md) to understand what to check in the message headers.

If the test fails, read the error message and check the most likely causes: wrong credential, unverified sender email, wrong region, disabled provider account, inactive domain, or a provider limit that prevents sending.

## Webhooks

Webhooks let your delivery provider tell Mailrith when an email bounces or when a subscriber marks an email as spam. When Mailrith receives those events, it updates the subscriber status to Bounced or Complained and protects future sends from repeatedly mailing bad or risky addresses.

To find webhook URLs, use the connection row action labeled **Webhooks**. Mailrith opens **Connection Webhooks** and shows the endpoint or endpoints to copy into the provider dashboard.

1. Click **Email Delivery Connections** in the left sidebar.
2. Find the connection you want to configure.
3. Click the row action labeled **Webhooks** to open **Connection Webhooks**.
4. Copy the Mailrith webhook URL or URLs for that provider.
5. Open the provider dashboard in another browser tab.
6. Paste the Mailrith URL into the provider's webhook, event, SNS, or notification settings.
7. Enable bounce and complaint or spam-report events.
8. Save the provider webhook settings and return to Mailrith.
9. Send a small test campaign or provider test event and confirm events arrive as expected.

- **Amazon SES:** uses Amazon SNS. Configure the Mailrith bounce endpoint for bounce notifications and the Mailrith complaint endpoint for complaint notifications.
- **Postmark, SendGrid, Mailgun, Resend, and Brevo:** use a single Mailrith delivery-event endpoint. Add the endpoint in the provider's webhook settings and enable bounce and complaint or spam events.
- **Custom SMTP:** Mailrith provides the same unified endpoint. Use it only if your SMTP provider or mail relay can send compatible bounce or complaint event payloads to a custom webhook URL.

Do not skip webhooks when your provider supports them. Without delivery events, Mailrith cannot automatically mark bad addresses as bounced or complained, which can damage deliverability over time.

For the concept behind these events, read [Bounces](https://mailrith.com/guides/bounces.md), [Spam Complaints](https://mailrith.com/guides/spam-complaints.md), and [Complaint Feedback Loops and ARF](https://mailrith.com/guides/complaint-feedback-loops-and-arf.md).

After configuring a webhook, run a small test or watch the provider dashboard after a real send. Some providers show whether webhook deliveries succeeded. If events are not appearing in Mailrith, check the exact URL, enabled event types, webhook secret or query parameter, and whether the provider is sending events for the same sender or stream used by the connection.

## Using Connections in Sends

Broadcasts, sequences, and automation email actions ask you to choose an email delivery connection. Mailrith only shows enabled connections assigned to the current workspace. If a connection is missing from the picker, check that it is enabled and assigned to that workspace.

Disable a connection when it should no longer be used for new sends but you still want to keep its history. Delete a connection only when you are sure no active campaigns, sequences, automations, or teammates need it.

Before a major launch, confirm four things: the selected connection sends a successful test email, the From email is the intended sender, the workspace assignment is correct, and the webhook is configured for bounce and complaint tracking.

If the connection will be used for a new sender, also review [Sending Volume and Warmup](https://mailrith.com/guides/start-small.md) so the first real campaigns go to engaged subscribers at a controlled pace.

## Related Guides
- [Set Up Amazon SES](https://mailrith.com/docs/setup-amazon-ses.md): Use Amazon SES when you want AWS-native sending with full control over your sending identity, regional configuration, and bounce tracking through SNS notifications.
- [Set Up Postmark](https://mailrith.com/docs/setup-postmark.md): Postmark is a strong choice for reliable transactional-style delivery — connect it to Mailrith with a server token, optionally specify a message stream, and configure one webhook endpoint for event tracking.
- [Set Up SendGrid](https://mailrith.com/docs/setup-sendgrid.md): SendGrid connects to Mailrith with an API key — configure the Event Webhook to keep subscriber statuses in sync when bounces or spam complaints occur.