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

# Email settings and domain authentication

> Configure outbound and inbound email behavior, including DNS-based domain authentication.

## Summary

Email setup is one of the most operationally sensitive areas in TruAgents.

The current app strongly suggests that email setup includes both:

* outbound sending configuration and domain authentication
* inbound email handling through forwarding or mailbox access

This should become one of the most detailed admin sections in the docs because small setup mistakes here can break the rest of the product flow.

## Who this is for

* Owners and admins
* Technical operators responsible for delivery and inbox setup
* Internal teammates helping customers validate email readiness

## Where to find it in the app

* **Settings → Email**

<img src="https://mintcdn.com/truagents/VZr9vfxgb7kk_70a/images/truagents-settings-email.png?fit=max&auto=format&n=VZr9vfxgb7kk_70a&q=85&s=1a44193a0a0c6c3b0bee97ed88f4b43a" alt="TruAgents email settings page showing outbound provider fields and inbound email options" width="3840" height="2160" data-path="images/truagents-settings-email.png" />

The current settings page already shows the two halves of email setup in one place: outbound sending on the left and inbound handling on the right.

## What this area appears to cover

### Outbound domain authentication

The app includes a domain-authentication flow with DNS records and verification behavior. That means the docs should explain:

* what domain is being authenticated
* which DNS records need to be added
* why verification can take time
* how users know whether setup succeeded or failed

### Inbound email handling

The app also supports incoming email configuration. The current UI suggests two broad approaches:

* forwarding email into TruAgents
* connecting directly to a mailbox

### Ongoing verification and troubleshooting

This page should eventually help users diagnose cases where DNS is incomplete, validation fails, or the sending setup is not ready yet.

## What the settings surface implies operationally

This is not just a provider-credentials page.

The current settings flow suggests admins are making decisions about:

* which provider path is active
* which sending domain the workspace should trust
* whether inbound email should use forwarding or direct mailbox access
* how much operational complexity the team is willing to own

## Example decision: forwarding vs mailbox access

| Option                | Best when                                                     | Watch out for                                                     |
| --------------------- | ------------------------------------------------------------- | ----------------------------------------------------------------- |
| Forwarding            | The team wants a simpler first inbound setup path             | Forwarding rules can be misconfigured silently                    |
| Direct mailbox access | The team wants tighter direct integration with a real mailbox | Credential and mailbox setup becomes more operationally sensitive |

## Recommended implementation order for customers

1. Open **Settings → Email**.
2. Configure outbound domain details first.
3. Add the required DNS records.
4. Wait for propagation and run verification.
5. Decide how inbound email should be handled.
6. Validate that the team understands which email path is now active.

## Outbound first, inbound second

That order matters.

Teams often want to configure everything at once, but the safer path is:

1. make outbound sending trustworthy
2. confirm verification status
3. then decide how replies will be handled

Simple version: get sending trust stable before optimizing reply handling.

## What "ready enough for first launch" means

* the sending domain has been configured
* required DNS records have been added
* the team can explain the current verification status
* inbound handling has been chosen intentionally, even if it is still basic

## Common mistakes

* mixing up sending-domain verification with inbound mailbox setup
* assuming one successful save means email is fully ready
* choosing inbound mode without deciding who will operate it
* diagnosing campaign issues before confirming email readiness
* expecting DNS-based verification to complete instantly

## If verification is not finishing

Start with the boring checks first:

1. confirm the DNS records were added to the correct domain
2. confirm the host/name and value fields were copied exactly
3. allow realistic time for propagation
4. verify whether the team is mixing up outbound authentication and inbound handling as if they are the same step

## Success checklist

* [ ] The sending domain is configured correctly.
* [ ] DNS records have been added and validated.
* [ ] The team understands whether inbound handling uses forwarding or direct mailbox access.
* [ ] The workspace is ready for campaign-related email activity without relying on placeholder setup.

## High-priority details to add later

* Exact DNS record examples and screenshots
* Expected statuses and what each one means
* How forwarding differs operationally from direct mailbox access
* What happens when verification fails or stalls

## Related pages

* [Connect email and SMS](/getting-started/connect-email-and-sms)
* [Integrations overview](/integrations/overview)
* [Email deliverability and DNS](/support/email-deliverability-and-dns)