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

# Domains and routes

> Set up a receiving domain and decide which recipients Talario accepts.

## Receiving domains

A domain receives email once two DNS records are valid:

| Type | Host | Value | Purpose |
| - | - | - | - |
| TXT | `_talario-receiving.<domain>` | `talario-verification=<token>` | Proves that you own the domain |
| MX | `<domain>` | `10 mail.talario.eu.` | Directs incoming email to Talario |

The dashboard shows the exact values. Talario must be the only MX of the domain; there is no fallback to another mail server.

Receiving and sending are independent. A domain that only receives email needs neither DKIM nor return-path records, and the domain list shows it as **Receiving only**.

Talario checks the records regularly. If a later check fails, receiving keeps working and the dashboard asks you to correct the records.

> [!TIP]
>
> Use a dedicated subdomain such as `inbound.example.com`. Changing the MX record of your main domain sends **all** of its email to Talario.

## Routes

Routes belong to a receiving domain. Each route has one filter, a priority and one or more actions.

### Filters

| Filter | Matches | Example |
| - | - | - |
| **Address** | exactly one recipient | `support@inbound.example.com` |
| **Pattern** | recipients whose local part matches; `*` is the only wildcard | `ticket+*@inbound.example.com` |
| **All recipients** | every valid address of the domain (catch-all) | |

* The local part (before the `@`) is compared without regard to ASCII case. The webhook keeps the recipient as the sender wrote it.
* Plus suffixes are not removed automatically. Use a pattern such as `ticket+*@…` to accept them.
* Routes of a domain do not apply to its subdomains.
* Unicode in the local part (SMTPUTF8) is not supported.

### Priority

Talario evaluates routes from the lowest priority (0) to the highest (65535). Routes with the same priority are evaluated in a fixed but unspecified order; use different priorities when the order matters.

### Actions

| Action | Effect |
| - | - |
| **Store** | Keep the message for 7 days so that your application can download it through the API. |
| **Webhook** | Deliver a webhook to an endpoint of the project. |
| **Stop** | Do not evaluate further routes for this recipient. |

A route needs at least one **Store** or **Webhook** action. Every accepted message is stored, also with **Webhook** only. If several routes deliver to the same endpoint for the same recipient, the endpoint receives one webhook, not several.

A domain can have up to 100 routes, each with up to 10 actions.

### When changes take effect

Changes to domains, routes and endpoints take effect as soon as the mail servers have applied them, usually within a minute. The dashboard shows the state next to each change. Routes apply to messages received afterwards; messages already received keep their routes and deliveries.


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