By default, all automated emails from SmartMoving send from [email protected]. Adding DKIM and Return-Path DNS records to your domain allows SmartMoving to send emails from your own address, improves deliverability, and reduces the chance your messages land in spam. These records verify to receiving mail servers that SmartMoving is authorized to send on your behalf.
Before You Start
You need access to your domain's DNS settings through your DNS provider (e.g., GoDaddy, Cloudflare, Namecheap), or know who manages them for you.
DNS changes can take up to 48 hours to propagate, though most update within a few hours.
After your records are verified, SmartMoving Support must update your System Email From Address. This step is not self-serve.
How To Do It
Step 1 — Request your DNS record values
During onboarding:
Reach the Connect Domain step in the Onboarding Wizard.
Select how your domain is managed:
I manage my domain settings — Enter your email address and click Send Email. SmartMoving sends your DNS record instructions to you.
I have someone who manages domain settings for me — Enter their name and email address, then click Send Email. SmartMoving sends the instructions to them and copies you.
Open the email and keep your DKIM record values handy for the steps below.
After onboarding:
Contact your SmartMoving Support ([email protected]) to request your DKIM and Return-Path record values. They will provide the exact hostname and value for your account.
Step 2 — Add your DNS records
You will need to add two records. Use the values from your instructions email for the DKIM record. The Return-Path values are the same for all SmartMoving accounts:
Record | Type | Hostname | Value |
DKIM | TXT | From your instructions (e.g., | From your instructions (begins with |
Return-Path | CNAME |
|
|
Note: If your DNS provider auto-appends your domain to hostname entries, enter only the prefix portion of the DKIM hostname (e.g., 20250314155159pm._domainkey) without your domain name.
Refer to your DNS provider's documentation for steps on adding records:
Provider | TXT Record Guide | CNAME Record Guide |
GoDaddy | ||
Cloudflare | ||
Namecheap | ||
Squarespace / Google Domains | ||
Wix |
Note: If you use Cloudflare, set the Return-Path CNAME record to DNS only (grey cloud icon), not proxied. Enabling the proxy on this record will break email authentication.
Step 3 — Notify SmartMoving to verify your records
After adding both records, contact your SmartMoving Support ([email protected]) to let them know your DNS records are in place. SmartMoving will verify the records and confirm when authentication is active.
💡 SmartTip: Before notifying support, confirm your records have propagated by looking up your domain at MXToolbox.
Step 4 — Update your System Email From Address
Once your records are verified, our Support Team will update your System Email From Address to your own domain.
About SPF and DMARC
SPF: You do not need to create an SPF record for SmartMoving emails. SmartMoving uses Postmark for email delivery, and Postmark handles SPF authentication automatically. No action is needed on your end.
DMARC: DMARC is a policy layer that builds on DKIM and SPF. SmartMoving does not currently provide DMARC setup steps. If your organization requires a DMARC policy, work with your IT team or DNS provider to configure it independently once your DKIM record is active and verified.
Best Practices
Add both the DKIM and Return-Path records at the same time — they work together for the best deliverability outcome.
Verify your records propagated using MXToolbox before notifying SmartMoving Support.
If emails still land in spam after setup, confirm the From address in your SmartMoving email templates matches the authenticated domain.
Do not delete or modify your DKIM or Return-Path records after setup. Removing them will cause authentication failures on outgoing emails.
Troubleshooting
Emails are still sending from [email protected] after records are verified.
The System Email From Address must be updated by SmartMoving Support. Contact them to complete this step if you have not already.
My DNS provider says the hostname is already in use.
A conflicting record may already exist. Remove it before adding the new one.
MXToolbox shows my DKIM record is not found.
Confirm the hostname and value were entered exactly as provided. A typo in either field will cause the lookup to fail. If the values look correct, wait a few more hours for propagation and check again.
Cloudflare is showing my CNAME as proxied.
Click the orange cloud icon next to the Return-Path CNAME record and switch it to DNS only (grey cloud). Proxied CNAME records will break email authentication.