> ## Documentation Index
> Fetch the complete documentation index at: /docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Avoid MX Conflicts

> How to set up Mailofly without disrupting existing Google Workspace or Microsoft 365 email.

A common concern when adding a domain to an email delivery service is accidentally breaking your company's existing business inboxes (such as Google Workspace or Outlook).

***

## The Rule of MX Records

MX (Mail Exchange) records dictate **where incoming mail is delivered**.

* If your apex domain (`yourcompany.com`) points to Google Workspace (`aspmx.l.google.com`), **do not modify your root MX records**.
* Mailofly only uses MX records for custom MAIL FROM return-path bounce handling or inbound routing on **subdomains**.

***

## Recommended Solution: Use a Subdomain

To ensure zero risk to your team's day-to-day corporate email:

1. Verify a dedicated subdomain such as:
   * `mail.yourcompany.com`
   * `updates.yourcompany.com`
   * `notifications.yourcompany.com`
2. Add the DKIM, SPF, and MX records exclusively on that subdomain.
3. Your corporate Gmail/Outlook inboxes on `yourcompany.com` will continue functioning without interruption.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.