Skip to main content
Your sending domain is the domain your email is sent from. Authenticating it with DNS records tells mailbox providers your mail is legitimate, which is essential for deliverability. Configure it in Settings → Domain.

​
Choose a domain

OptionWhen to use
Custom domainRecommended for production. Send from your own domain (e.g. mail.yourcompany.com).
System domainGet started quickly on your-workspace.railmail.com. Carries Railmail branding.

​
Verify with DNS

1

Copy the records

Railmail shows the SPF, DKIM and DMARC records to add. For each, note its name, value and TTL.
2

Add them at your DNS provider

Create the records in your domain’s DNS settings. Changes can take some time to propagate.
3

Verify

Back in Railmail, click Verify DNS. Once the records are found, the domain becomes verified.
Railmail also shows a domain health / reputation score so you can monitor how mailbox providers view your domain.

​
Warming

New domains are warmed: they send under a daily quota that increases over time, moving from an initial phase toward a mature one. This protects your sender reputation. You can monitor the daily limit, bounce rate and complaint rate, and pause or resume warming.
The warming quota can cap how many recipients a campaign reaches per day. If a send is limited, that’s expected during warming.

​
Domain statuses

StatusMeaning
ActiveVerified and sending.
Pending verificationWaiting for DNS records to be found.
Verification failedRecords not found or incorrect.
DegradedReputation or configuration issue.
Suspended / BlockedSending stopped due to a serious issue.
ExpiredVerification needs to be renewed.
Under Settings → Email, configure the compliant footer added to every email: company name and address, and the wording for the unsubscribe and preference-center links (always included). You can add custom footer text, and remove the Powered by Railmail badge on paid plans.