Email Delivery Connections

Supported Email Delivery Services

Mailrith manages subscribers, campaigns, automations, and reports. Your email delivery service sends each message. This setup lets you choose the service that fits your business and see its sending costs and limits separately.

A delivery connection stores the service connection details, sender name and address, delivery-event settings, and the workspaces that can use that sender. You need at least one enabled connection assigned to the workspace before you can create broadcasts, sequences, automations, forms, or landing pages that may send email.

Mailrith supports these email delivery services:

• Amazon SES: use this when your team already uses AWS and needs regional control, verified identities, and SNS-based delivery events.
• Postmark: use this when you want a focused email delivery service with server and account tokens, message streams, and clear delivery events.
• SendGrid: use this when your team already uses SendGrid API keys and Event Webhooks.
• Mailgun: use this when you send from a verified Mailgun domain and need to choose the correct US or EU region.
• Resend: use this when you want a straightforward connection with a verified domain.
• Brevo: use this when your sender identity and transactional email setup already live in Brevo.
• Custom SMTP: use this 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 workspace uses a client-specific sender, or one team can keep a test sender separate from the sender used for production campaigns.

If the setup terms are unclear, read Email Delivery Services, Email Types and Sender Separation, and Sender Domains and Email Authentication before you choose a connection.

Email Delivery Service Setup Guides

Each service has different setup steps and names for its connection details. Follow the guide for your service before you create the connection:

• Set Up Amazon SES for AWS region, access key, secret key, verified identity, and SNS events.
• Set Up Postmark for server token, account token, optional message stream, and Postmark webhooks.
• Set Up SendGrid for API key, sender authentication, and Event Webhook setup.
• Set Up Mailgun for API key, sending domain, region, and webhook routing.
• Set Up Resend for API key, verified domain, and webhook setup.
• Set Up Brevo for API key, verified sender, and webhook setup.
• Set Up Custom SMTP for host, port, security mode, username, password, and optional event forwarding.

If you are not sure which service to choose, start with the service where your domain is already verified. You can change services later, but the first setup is usually easier when you continue from an existing verified domain.

Create And Test A Connection

1. Click Email Delivery Connections in the left sidebar.
2. Click Create Connection in the page header.
3. In Select Email Delivery Service, select the service 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 that subscribers will see in their inbox.
6. Use Workspaces to assign the connection only to the workspaces that are allowed to send from this identity.
7. Enter the connection details shown for that service, such as API Key, Server API Token, Account 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 you use 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 address subscribers see. This address or its domain must be approved by the email delivery service.
• Service connection details: the key, token, AWS key, Custom SMTP details, or other secret that Mailrith needs to send through the service.
• Workspace assignment: the workspaces that can use this connection. If a connection is assigned to the wrong workspace, the connection will not appear in the sender picker where you expect it.

After you save the connection, send a test email before you use the connection in a real campaign. The test checks the most important parts of setup: Mailrith can connect to the service, the service allows the sender name and address, and 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 and DMARC Alignment to learn which message headers to check.

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

Return Bounces And Complaints With Webhooks

A webhook is a delivery-event link that lets your email delivery service tell Mailrith when an email bounces or when a subscriber marks an email as spam. Mailrith then changes the subscriber status to Bounced or Complained and prevents future sends to that address.

To find these links, use the connection row action labeled Webhooks. Mailrith opens Connection Webhooks and shows the link or links that you need to copy into the email delivery service.

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 service.
5. Open the email delivery service in another browser tab.
6. Paste the Mailrith URL into the service's webhook, event, SNS, or notification settings.
7. Enable bounce and complaint or spam-report events.
8. Save the service settings and return to Mailrith.
9. Send a small test campaign or service test event, then confirm that Mailrith records the expected bounce or complaint updates for the connection.

• 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 link. Add the link in the service's webhook settings and enable bounce and complaint or spam events.
• Custom SMTP: Mailrith provides the same delivery-event link. Use it only if your email delivery service or mail relay can send compatible bounce or complaint updates to a custom webhook URL.

Do not skip webhooks when your email delivery service supports them. Without delivery events, Mailrith cannot automatically mark bad addresses as bounced or complained, and repeated sends to those addresses can harm future delivery.

For the concept behind these events, read Bounces, Spam Complaints, and Complaint Feedback Loops and ARF.

After you configure a webhook, run a small test or watch the email delivery service after a real send. Some services show whether the update reached Mailrith. If events do not appear, check that the webhook URL is exact, bounce and complaint events are enabled, the secret or query parameter is correct, and the service 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 every connection assigned to a workspace is disabled, Mailrith blocks new broadcasts, sequences, automations, forms, and landing pages until someone enables or creates a connection.

Disable a connection when new sends should stop using it but you still need to keep its history. Delete a connection only after you confirm that 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 so the first real campaigns go to engaged subscribers at a controlled pace.