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

# Email configuration

> Configure a custom sender domain so Tilta sends buyer emails from your domain – subdomain delegation or main domain setup with full DNS record guidance.

Tilta can send buyer-facing emails from your own domain, so every communication your buyers receive appears to come directly from your platform rather than from a generic Tilta address. You have two options: delegating a subdomain entirely to Tilta (the simpler path), or configuring Tilta to send from an address on your main domain (which requires additional routing setup). Both options use the same DNS-based authentication infrastructure.

<Tabs>
  <Tab title="Option 1 – subdomain (recommended)">
    ## Sending from a Subdomain

    Delegating a dedicated subdomain to Tilta is the recommended approach. It requires no changes to your main domain's DNS records or email routing, which avoids any risk of disrupting existing email flows. Tilta handles all sending, bounces, and link tracking through the subdomain you assign.

    ### Choose Your Subdomain

    Pick a new, unused subdomain that has never been used for email before. Using an existing subdomain that already has MX records or SPF policies can cause delivery conflicts. Good options include:

    * `accounts.your-domain.com`
    * `invoicing.your-domain.com`
    * `billing.your-domain.com`
    * `pay.your-domain.com`

    <Warning>
      Do not reuse a subdomain that already handles email or has existing MX records. Create a brand-new subdomain specifically for Tilta. If you have any doubt, check with your DNS administrator before proceeding.
    </Warning>

    ### DNS Records

    Add the following DNS records for your chosen subdomain (replace `subdomain` with your chosen name and `your-domain.com` with your actual domain):

    | Type    | Host                         | Value                                                           | Purpose                              | Required?      |
    | ------- | ---------------------------- | --------------------------------------------------------------- | ------------------------------------ | -------------- |
    | `MX`    | `subdomain`                  | `inbound.tilta-emails.io`                                       | Receiving email (inbound routing)    | ✅ Required     |
    | `CNAME` | `tilta-bounce.subdomain`     | `bounce.tilta-emails.io`                                        | Bounce handling for outbound sending | ✅ Required     |
    | `CNAME` | `tilta-tracking.subdomain`   | `tracking.tilta-emails.io`                                      | Link click tracking                  | ✅ Required     |
    | `CNAME` | `tilta._domainkey.subdomain` | `tilta.dkim.tilta-emails.io`                                    | DKIM email authentication            | ✅ Required     |
    | `TXT`   | `_dmarc.subdomain`           | `v=DMARC1; p=none; rua=mailto:report@subdomain.your-domain.com` | DMARC reporting                      | 📋 Recommended |

    <Note>
      The MX record for your subdomain routes any inbound replies to Tilta's infrastructure, which handles them appropriately (for example, processing out-of-office replies to suppress notifications). This record does not affect email delivery on your main domain.
    </Note>

    ### Setup Steps

    <Steps>
      <Step title="Choose and reserve your subdomain">
        Decide on a subdomain name (e.g., `invoicing`) and confirm it is unused – no existing MX records, A records pointing to an email server, or prior SPF entries. Reserve it in your DNS zone by noting the full subdomain: `invoicing.your-domain.com`.
      </Step>

      <Step title="Add the required DNS records">
        Log in to your DNS provider and add all four required records from the table above. Use your chosen subdomain name in place of `subdomain`. DNS propagation typically takes between a few minutes and 48 hours depending on your provider and TTL settings.
      </Step>

      <Step title="Add the DMARC record (recommended)">
        Add the `TXT` record for `_dmarc.subdomain` with the DMARC policy shown in the table. Using `p=none` starts in monitor mode, letting you review DMARC reports without rejecting any mail – upgrade to `p=quarantine` or `p=reject` after confirming legitimate mail is authenticating correctly.
      </Step>

      <Step title="Provide your subdomain to Tilta">
        Share the full subdomain (e.g., `invoicing.your-domain.com`) with your Tilta integration manager. Tilta verifies the DNS records and activates sending from your subdomain. You will receive confirmation once the domain is live.
      </Step>
    </Steps>

    ### SPF Alignment Note

    Strict SPF alignment (`aspf=s` in your DMARC policy) is **not supported** for subdomain configurations. Use relaxed alignment (`aspf=r`, which is the DMARC default) to ensure emails pass authentication checks.
  </Tab>

  <Tab title="Option 2 – main domain">
    ## Sending from Your Main Domain

    If you want buyer emails to come from an address at your primary domain (for example, `invoicing@your-company.com`), you can configure Tilta to send from a dedicated mailbox on your main domain. This option requires you to set up email redirection from your mailbox to Tilta's inbound infrastructure, in addition to the DNS changes.

    ### Choose Your Address

    Select a new, unused email address at your main domain. This address must not already be in active use – it will be dedicated to Tilta's sending. Good options include:

    * `accounts@your-domain.com`
    * `invoicing@your-domain.com`
    * `billing@your-domain.com`
    * `pay@your-domain.com`

    <Warning>
      Do not repurpose an existing active mailbox. The redirection rule you will configure sends all incoming mail to Tilta's infrastructure. Use a fresh address created specifically for this purpose.
    </Warning>

    ### Set Up Email Redirection

    You must configure your email provider to redirect (forward at the envelope level) all incoming mail for your chosen address to `inbound@tilta-emails.io`. The `To:` header in the message is left unchanged – only the SMTP envelope recipient is redirected.

    <Steps>
      <Step title="Microsoft 365 – configure a mail flow rule">
        <Steps>
          <Step title="Open Exchange Admin Center">
            Sign in to the [Exchange Admin Center](https://admin.exchange.microsoft.com) with an account that has Exchange Administrator or Global Administrator privileges.
          </Step>

          <Step title="Navigate to mail flow rules">
            Go to **Mail flow** → **Rules** in the left-hand navigation.
          </Step>

          <Step title="Create a new rule">
            Click **+ Add a rule** → **Create a new rule**. Give it a descriptive name such as "Tilta Inbound Redirect".
          </Step>

          <Step title="Set the condition">
            Under **Apply this rule if**, select **The recipient is** and enter your chosen address (e.g., `invoicing@your-domain.com`).
          </Step>

          <Step title="Set the action">
            Under **Do the following**, select **Redirect the message to** and enter `inbound@tilta-emails.io`. This redirects the SMTP envelope only – the original `To:` header is preserved as required.
          </Step>

          <Step title="Save and enable">
            Save the rule and confirm it is set to **Enabled**. Send a test message to your chosen address to verify the redirection is working.
          </Step>
        </Steps>
      </Step>

      <Step title="Google Workspace – configure default routing">
        <Steps>
          <Step title="Open Google Admin Console">
            Sign in to the [Google Admin Console](https://admin.google.com) as a Super Administrator.
          </Step>

          <Step title="Navigate to Gmail routing settings">
            Go to **Apps** → **Google Workspace** → **Gmail** → **Default routing**.
          </Step>

          <Step title="Add a routing rule">
            Click **Add another rule** (or **Configure** if no rules exist yet). Give the rule a name such as "Tilta Inbound Redirect".
          </Step>

          <Step title="Set the envelope recipient condition">
            Under **Email messages to affect**, select **Inbound**. Under **Envelope recipient**, select **Match one or more addresses or domains** and enter your chosen address (e.g., `invoicing@your-domain.com`).
          </Step>

          <Step title="Configure the routing action">
            Under **Also deliver to**, select **Add more recipients** and enter `inbound@tilta-emails.io`. Ensure you are routing the **envelope recipient** – do not modify the message headers.
          </Step>

          <Step title="Save and test">
            Save the rule. Send a test email to your chosen address and confirm it is delivered to Tilta's inbound address.
          </Step>
        </Steps>
      </Step>
    </Steps>

    ### DNS Records

    Add the following DNS records to your main domain's zone (replace `your-domain.com` with your actual domain):

    | Type    | Host               | Value                                                 | Purpose                              | Required?      |
    | ------- | ------------------ | ----------------------------------------------------- | ------------------------------------ | -------------- |
    | `CNAME` | `tilta-bounce`     | `bounce.tilta-emails.io`                              | Bounce handling for outbound sending | ✅ Required     |
    | `CNAME` | `tilta-tracking`   | `tracking.tilta-emails.io`                            | Link click tracking                  | ✅ Required     |
    | `CNAME` | `tilta._domainkey` | `tilta.dkim.tilta-emails.io`                          | DKIM email authentication            | ✅ Required     |
    | `TXT`   | `_dmarc`           | `v=DMARC1; p=none; rua=mailto:report@your-domain.com` | DMARC reporting                      | 📋 Recommended |

    <Warning>
      If your main domain already has a `_dmarc` TXT record, do not replace it – work with your IT team or email administrator to update the existing record appropriately. Modifying DMARC on an active sending domain without review can disrupt your existing outbound email authentication and cause legitimate emails to be rejected or quarantined. Strict SPF alignment (`aspf=s`) is **not supported** – ensure your DMARC policy uses relaxed alignment.
    </Warning>

    ### Provide Your Address to Tilta

    Once redirection is working and DNS records are in place, share your chosen sender address (e.g., `invoicing@your-domain.com`) with your Tilta integration manager. Tilta will verify the configuration and activate sending. You will receive confirmation once the address is live.
  </Tab>
</Tabs>

***

## Verifying your setup

After completing your chosen configuration and notifying your Tilta integration manager, Tilta performs DNS verification before activating your custom sender. To avoid delays:

* Confirm all required DNS records are published and resolving correctly (use a tool like `dig` or an online DNS checker)
* Allow up to 48 hours for DNS propagation if you have recently made changes
* Test your email redirection (for the main domain option) before submitting to Tilta for verification

<Tip>
  You can use the sandbox environment (`https://api.tilta-sandbox.io`) to trigger buyer email flows and verify that emails are sent from your configured address before going live in production.
</Tip>

***

## Frequently asked questions

<Accordion title="Can I use the same subdomain for both inbound and outbound?">
  Yes – the MX record on your subdomain handles inbound routing (for replies and bounce handling), while the CNAME records handle outbound authentication (DKIM, bounce domain, tracking). All four required records work together on the same subdomain.
</Accordion>

<Accordion title="What happens if I don't configure a custom sender domain?">
  Tilta falls back to a Tilta-hosted domain for sending. Emails will still display your platform's name and logo in the body, but the sender address and domain will be Tilta's rather than yours. For the best buyer experience and deliverability, configuring a custom sender domain is strongly recommended.
</Accordion>

<Accordion title="Why is strict SPF alignment not supported?">
  Tilta's sending infrastructure sends on behalf of your domain using its own mail servers. Strict SPF alignment (`aspf=s`) requires the `From` header domain to exactly match the envelope sender domain, which is not compatible with this architecture. Relaxed alignment (`aspf=r`), which is the DMARC default, allows the subdomain or sending domain relationship and works correctly with Tilta's setup.
</Accordion>

<Accordion title="How long does domain verification take?">
  Once you have added all DNS records and notified your Tilta integration manager, verification typically completes within one business day – assuming DNS has fully propagated. Complex DNS setups or propagation delays may extend this timeline.
</Accordion>