Improve your email deliverability and meet modern authentication standards—SPF, DKIM, and DMARC—by configuring Enhanced Delivery with a custom email domain through Mailgun. This article walks technical teams through setting up DNS records and domain verification to ensure your Maxio Advanced Billing emails are properly authenticated and delivered.
This article is intended for technically advanced audiences who manage your organization's email infrastructure. We recommend sharing this information with your IT team to help resolve any email deliverability issues.
We strongly recommend testing any changes to your email setup in a test environment before applying them to your live site. This approach helps identify and resolve potential issues before they impact live email delivery.
Custom Email Domain with Enhanced Delivery
To improve email deliverability and comply with modern email authentication standards (including SPF, DKIM, and DMARC), Maxio offers a self-service Enhanced Delivery feature. This feature enables you to send emails from a custom domain via Mailgun, improving authentication and helping achieve DMARC compliance.
Enhanced Delivery allows Maxio Advanced Billing to send emails on your behalf through our Mailgun account, using your verified domain with full SPF, DKIM, and DMARC support. This does not require you to maintain a separate Mailgun account. However, your domain admin must complete several DNS configuration steps.
For more details about sender requirements enforced by Google and Yahoo, refer to: https://www.mailgun.com/blog/deliverability/gmail-and-yahoo-inbox-updates-2024/
FAQs on Enhanced Email Delivery
-
What steps are needed to activate Enhanced Delivery?
You’ll create DNS records to set up a custom sending subdomain. -
Will this affect other email services on my domain?
No. Maxio Advanced Billing will only send from a designated subdomain, such as "maxio.example.net". Other domain services remain unaffected. -
Is there any cost to use Enhanced Delivery through Maxio?
No additional cost is incurred. We recommend enabling it first on a test site, then applying the configuration to your live site.
Admin users can access this feature from the Tools > Email Insights > Setup Info page within the "Mailgun setup" section of your Advanced Billing site:
We strongly recommend this setup be performed by your IT representative. Misconfiguration may result in email delivery failures.
First, identify the domain you'll use for sending. This may be a new or previously connected domain.
Then, configure TXT and CNAME DNS records. These will vary depending on whether you use a root domain or a subdomain. Key elements include domainkey, @, and email.
Root Domain Example:
| Name | Record Type | Example Value |
|---|---|---|
| smtp._domainkey | TXT | k=rsa; p=MIGfXXXXXXXXXXXXX |
| @ | TXT | v=spf1 include:mailgun.org ~all |
| CNAME | mailgun.org |
Subdomain Example (e.g., "maxio"):
| Name | Record Type | Example Value |
|---|---|---|
| smtp._domainkey.maxio | TXT | k=rsa; p=MIGfXXXXXXXXXXXXX |
| maxio | TXT | v=spf1 include:mailgun.org ~all |
| email.maxio | CNAME | mailgun.org |
Once the DNS records are added, click "Check DNS Records Now" to verify. This process may take 24–48 hours. If the check returns an "unverified" status, review the DNS entries and values for accuracy.
After achieving a "verified" status, proceed to test email delivery.
Advanced Billing uses the “From” address you specify in your site settings as the email sender. For guidance on setting this value, see the Quick Start Guide.
Mailgun's MX Records (Optional)
If your subdomain does not already have MX records, you may add Mailgun's MX records to help prevent "Sender Domain Verification" bounce errors.
Mailgun MX Records:
| Value | Priority |
|---|---|
| mxa.mailgun.org | 10 |
| mxb.mailgun.org | 10 |
Comments
Article is closed for comments.