# Limit an inbox’s recipients

Choose the addresses and domains an inbox may email, with rules only you can change.

Source: https://cherami.to/docs/guides/sending-rules



Open [Account → Sending rules](https://cherami.to/account/sending-rules), select an inbox, and enter its allowed recipients in the **Email addresses** and **Domains** tabs, one per line. Turn on **Restrict recipients**, then choose **Save rules**. Each inbox starts unrestricted, and its rules apply to every agent sending from it, over HTTP or MCP.

With restrictions on, every To, Cc and Bcc recipient must match an allowed address or domain, in replies, reply-all and forwards too. If one doesn't, the send fails with `403 recipient_not_allowed` naming the blocked recipients, and nothing is sent or charged. Add the recipient to the rules or remove it from the send. With both lists empty, the inbox can't send at all.

Turn restrictions off to send to anyone again; your lists stay saved. These rules narrow who the inbox can email; [permitted sending](https://cherami.to/docs/guides/safety#permitted-sending) covers who you may email at all.

## Choose addresses and domains [#choose-addresses-and-domains]

Enter bare ASCII email addresses, without display names or wildcards, and bare domains such as `example.com`, using punycode for internationalized domains (`xn--bcher-kva.de`). Each list holds up to 100 entries.

The part before `@` is case-sensitive: `Alex@example.com` and `alex@example.com` are different entries. Domain case doesn't matter. Plus tags and dots make different addresses, even when a provider delivers them to the same mailbox.

A domain rule matches only that exact domain: `example.com` allows `alex@example.com`, but not `sub.example.com` or `notexample.com`. Add subdomains separately.

## Let the agent inspect the rules [#let-the-agent-inspect-the-rules]

Agents can read the rules with `get_sending_policy` or [over HTTP](https://cherami.to/docs/api/inboxes/get-sending-policy). Only you can change them, from Account.
