Email Delivery Services
An email delivery service sends your email, while Mailrith manages subscribers, campaigns, and follow-up.
Overview
Mailrith is where you plan subscribers, write the email, choose the sender, schedule the campaign, and review results. The email delivery service accepts the message from Mailrith and delivers it to receiving inboxes.
Mailrith has built-in connection steps for supported email delivery services. If your service is not listed, Custom SMTP may let you connect it with the host, port, username, and password supplied by that service.
A built-in connection usually needs fewer choices because the guide is written for that service. Custom SMTP is useful when Mailrith does not have a built-in connection or when an organization uses its own mail relay.
SMTP is not the same as a normal inbox login. A mailbox lets a person read email, while SMTP submits outgoing email. Some SMTP services require app passwords, IP allowlists, or specific sender permissions before SMTP sending works.
The email delivery service often manages domain verification, custom DKIM, custom return-path, bounce handling, complaint handling, rate limits, and account reputation. Mailrith can use the connection, but Mailrith cannot make an unverified sender trustworthy by itself.
For this reason, complete the email delivery service setup before you set up a campaign. If the email delivery service account cannot send from the chosen From email, or if DNS authentication is incomplete, the campaign editor cannot fix the delivery problem.
What to Do
- Choose the email delivery service that should send this type of email.
- Verify the sender domain or sender address inside that email delivery service before creating a Mailrith campaign.
- Prefer the built-in connection when Mailrith supports the email delivery service you use.
- Use Set Up Custom SMTP only when your email delivery service or mail server supplies the required Custom SMTP details.
- Confirm that your email delivery service signs email with your domain using DKIM and, where possible, uses a custom return-path for SPF.
- Create the Email Delivery Connection in Mailrith and assign it only to the correct workspaces.
- Send a test email, then inspect the test email and delivery result before using the connection in a broadcast, sequence, or automation.
- Set up email delivery service webhooks so Bounces and Spam Complaints can update subscriber status in Mailrith.
What to Check
- Built-in service connections usually give Mailrith the clearest delivery updates.
- SMTP sending requires the correct host, port, security mode, username, password, and allowed From email.
- A successful SMTP login does not prove that SPF, DKIM, DMARC, or alignment are correct.
- Email delivery service rate limits and account policies can still block or slow a send after Mailrith submits the message.
- Use an email delivery service that shows bounces, complaints, suppressions, and rejected messages.
- If you manage your own SMTP server, you are also responsible for TLS, PTR, queue health, abuse prevention, and IP reputation.
Note
Mailrith controls the campaign. Your email delivery service controls the sending infrastructure. A healthy send requires both systems to be configured correctly.