Custom Domain Email Setup Checklist

Document display names, aliases, forwarding rules, delegates, and mailbox owners. The business email account structure guide provides additional criteria for separating personal, team, and automated addresses.

Configure DNS and sender authentication

Your email provider will supply the required records. Copy values exactly, including hostnames, priorities, selectors, and trailing punctuation where applicable. DNS interfaces vary, so confirm whether the provider expects a full hostname or automatically appends your domain.

Configure these core records:

1. MX records: Point inbound mail to the designated servers. Remove obsolete MX records unless your provider explicitly requires them.
2. SPF: Publish one SPF TXT record that authorizes every legitimate sending service. Do not create separate SPF records for different tools; combine authorized sources correctly.
3. DKIM: Add the provider’s selector record and enable signing in the email service. Each sending platform may use a different selector.
4. DMARC: Publish a policy that identifies aligned mail and provides handling instructions. A monitored p=none policy is a useful starting point while you inventory senders, but it should not become a substitute for enforcement planning.

Use the SPF, DKIM and DMARC guide to review alignment and policy choices. Send aggregate DMARC reports to a controlled address, restrict access to them, and retain them only as long as operationally necessary.

Lowering DNS time-to-live values before migration can make planned changes easier to revise, but do not assume every resolver updates immediately. Keep old service settings available until testing confirms the new route works.

Set up secure mailbox and application access

Require unique passwords and multi-factor authentication for administrators and users. Disable legacy or unused authentication methods where possible. Limit administrative privileges to people who need them, and use separate day-to-day and administrator accounts when supported.

For mail applications, prefer encrypted connections. IMAP commonly uses TLS on port 993. SMTP submission commonly uses STARTTLS on port 587, while some providers support implicit TLS on port 465. Always follow the service’s documented hostnames and ports rather than guessing. Use OAuth or provider-issued application passwords when available instead of placing a primary password in multiple apps.

Email Friend offers Webmail, SMTP and IMAP, from $70 per plan. This is current listed starting pricing; confirm the plan scope and current details before purchase.

Migrate mail without losing continuity

Inventory every mailbox, alias, forwarding rule, contact list, calendar, shared folder, automated sender, and connected application. Remove abandoned accounts before migration, but preserve records subject to business or legal retention requirements.

Choose a cutover window with support coverage. Create destination mailboxes first, verify credentials, and run an initial message transfer if your migration method supports it. Then change the MX records, complete a final synchronization, and keep the previous environment accessible until users confirm that recent and historical messages are present.

Give users the new webmail address, application settings, MFA instructions, and a clear time for switching. Update scanners, website forms, customer relationship systems, invoicing tools, and other devices that send mail. Never use a personal mailbox password in a shared device; create a restricted account or approved application credential.

Test, document, and administer the system

Complete this checklist before closing the project:

• [ ] Send and receive messages internally and with external domains
• [ ] Verify SPF, DKIM, and DMARC results in message headers
• [ ] Test replies, aliases, shared addresses, and forwarding rules
• [ ] Confirm webmail, IMAP, and authenticated SMTP access
• [ ] Test password recovery and administrator access
• [ ] Check website forms and business applications
• [ ] Record DNS values, mailbox owners, and support procedures
• [ ] Schedule account, forwarding, and access reviews

If the domain will be used for outreach, identify and document an appropriate lawful basis, such as consent or legitimate interest where applicable. Provide a working opt-out, honor requests promptly, and maintain a suppression list so removed contacts are not re-imported. Minimize collected contact data, restrict access, and avoid retaining information without a defined purpose. Before launching outreach, review the audience and sending process when you start a campaign.

Ongoing administration matters as much as initial configuration. Review administrator access, inactive accounts, authentication reports, renewal contacts, and connected applications on a regular schedule. Remove access promptly when responsibilities change.

Conclusion: A reliable custom domain email setup has clear ownership, deliberate mailbox design, authenticated DNS, secure protocols, a reversible migration, and repeatable tests. Keep a current configuration record so future administrators can maintain the system without reconstructing how it works.