Prerequisites
Before setting up email receiving, ensure you have:- A verified Lettr account
- Access to your domain’s DNS settings
- A webhook endpoint ready to receive inbound email events (recommended)
Step-by-Step Setup
Add an Inbound Domain
Navigate to Domains → Inbound in your dashboard and click Add Domain. Enter the domain or subdomain you want to use for receiving emails.
Configure MX Records
Add the provided MX records to your domain’s DNS settings. These records tell email servers to route mail to Lettr.
Adding an Inbound Domain
- Go to Domains → Inbound
- Click Add Domain
- Enter your domain (e.g.,
mail.example.com) - Click Create
unverified until DNS is configured).
Inbound domain management is available through the Lettr dashboard. There is no public API endpoint for creating or managing inbound domains.
DNS Configuration
Add these MX records to your domain’s DNS settings:| Type | Host/Name | Priority | Value |
|---|---|---|---|
| MX | @ or subdomain | 10 | rx1.sparkpostmail.com |
| MX | @ or subdomain | 10 | rx2.sparkpostmail.com |
| MX | @ or subdomain | 10 | rx3.sparkpostmail.com |
If you’re using a subdomain like
mail.example.com, set the Host/Name field to mail instead of @.Understanding MX Priority
All three MX records use the same priority (10), which provides load balancing:| Priority | Server | Purpose |
|---|---|---|
| 10 | rx1.sparkpostmail.com | Mail server |
| 10 | rx2.sparkpostmail.com | Mail server |
| 10 | rx3.sparkpostmail.com | Mail server |
Verifying Your Domain
After adding MX records, verify they’re properly configured:- Go to Domains → Inbound
- Find your domain and click Verify
- Wait for the verification to complete
unverified to valid, confirming your MX records are correctly configured.
Domain Status
| Status | Description |
|---|---|
valid | All MX records found and configured correctly |
unverified | MX records not yet detected or incomplete |
Using Subdomains vs Root Domain
We recommend using a subdomain for inbound email:| Configuration | Use Case |
|---|---|
mail.example.com | General inbound processing |
reply.example.com | Reply tracking for transactional emails |
support.example.com | Customer support emails |
inbound.example.com | Webhook-triggered workflows |
DNS Propagation
DNS changes can take time to propagate:| Typical Time | Description |
|---|---|
| 5 minutes | Most DNS providers |
| 1-4 hours | Some registrars |
| Up to 48 hours | Worst case |