What you need before you start
Business email on your own domain gives your team addresses such as name@yourcompany.com. You need ownership of that domain and access to the place where its DNS records are managed. Registering a domain and hosting email are separate services.
If your domain already receives mail, record the existing MX and email-authentication settings. Keep the current service active while you prepare and test the new one. Changing an MX record changes where new incoming mail is routed; it does not copy historical messages.
1. Verify that the domain belongs to you
Create an administrator account with a private email address, then create your organization and add your domain. RelyPost provides an ownership record in the domain setup workflow. Copy the exact name and value into your DNS provider, then request verification.
Use the records generated for your own domain. A sample token or another organization’s DKIM key will not verify your ownership. DNS updates can take time to become visible; check the values before repeatedly replacing records.
2. Prepare the team’s mailboxes
Create a personal mailbox for each teammate who needs an individual sign-in. Use an alias when an additional address should lead to an existing mailbox. Use a shared mailbox, on an eligible plan, when several people need to manage the same conversation history.
Decide who can administer the organization and who can read or reply from shared mailboxes. Give each person their own credentials. Review your plan’s mailbox, storage and sending allowances before moving the whole team.
3. Configure mail routing and authentication
Follow the exact MX, SPF and DKIM records shown in your workspace. MX directs incoming mail to the receiving service. SPF identifies authorized sending systems. DKIM lets a receiving system verify a cryptographic signature on messages.
DMARC ties authentication to the visible From domain and expresses a handling policy. If you still send through another service, account for it before tightening your policy. Do not publish multiple separate SPF records at the same hostname; maintain one policy that includes the senders you authorize.
4. Import, test and finish the move
Connect the old account through the import workflow using an available provider method. Check representative folders, message dates and attachments after the import. Keep the source account available until you have verified the result and resolved any failures.
Test incoming and outgoing mail with accounts you control. Check replies, attachments, authentication results and shared-mail permissions. Connect compatible desktop or mobile email apps using TLS and a separate app password. Revoke temporary migration credentials when they are no longer needed.
Next: Understand SPF, DKIM and DMARC
Need help with your setup? Contact RelyPost support or compare plans.
← All guides