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

# Forwarding Rules

> Map addresses on your domain to external destinations

## What a rule does

A forwarding rule maps a localpart on your domain to a single destination email address:

```
support@yourdomain.com → team@yourinbox.com
```

Mail to `support@yourdomain.com` is filtered, then re-sent to `team@yourinbox.com`. You can have many rules per domain (up to **200**), and the same localpart can fan out to multiple destinations.

Manage rules from **Inbound → your domain → Forwarding** in the [Dashboard](https://dash.jetemail.com).

## Adding rules

<Steps>
  <Step title="Open the Forwarding tab">
    Pick your forwarding domain in **Inbound** and switch to the **Forwarding** tab. If you don't see it, the domain isn't in forwarding mode. Change it on the **Settings** tab first.
  </Step>

  <Step title="Add an address">
    Under **Forwarding rules**, enter the localpart (e.g. `support`) and a destination (e.g. `team@yourinbox.com`), then **Add rule**. The destination has to be a bare email address, with no display names or quoted parts.
  </Step>

  <Step title="Verify the destination">
    The first time you send mail to a destination, the destination owner gets a confirmation email. Until they click the link, mail to that rule won't be delivered. See [Destination Verification](/inbound/forwarding/destination-verification).
  </Step>
</Steps>

## Catch-all

A catch-all forwards every address on your domain that doesn't match a specific rule. Without one, unmatched mail is rejected with `550`.

Add a catch-all from the **Catch-all** card on the Forwarding tab. You only need to provide a destination. Specific rules always take precedence over the catch-all, so `support@yourdomain.com` still hits its own rule even with a catch-all in place.

## Plus-addressing

Plus-addressing matches automatically. A rule for `support` will also match:

* `support+sales@yourdomain.com`
* `support+ticket-1234@yourdomain.com`
* any other `support+...` variant

You don't need a separate rule per suffix.

## Pause, edit, delete

Each rule has three controls:

* **Pause / Resume**: soft-disables a rule without deleting it. Paused rules behave as if they don't exist (mail falls through to the catch-all or is rejected). Use this instead of deleting if you'll re-enable later.
* **Edit**: change the destination without losing the rule. The localpart is immutable; to rename, delete the rule and create a new one.
* **Delete**: removes the rule. The destination row in your account stays around, so re-pointing another rule at the same address won't trigger another verification email.

## Limits

* **200 rules per domain.** The Forwarding tab shows a `count / 200` badge that turns yellow at 180.
* **Localpart max 64 characters.** Standard RFC 5321. Anything that's a valid local-part is allowed except special characters that break SMTP routing.
* **Destinations must be bare addresses.** `team@yourinbox.com`, not `Support Team <team@yourinbox.com>`.