Email Forwarders
A forwarder redirects mail sent to an address on your domain to one or more other addresses, without needing a mailbox behind it. [email protected] can fan out to three colleagues' inboxes, wherever those live.
Email → Forwardershttps://YOUR-SERVER-IP:8443/email/forwarders| Source | Destinations | Status | Actions |
|---|---|---|---|
| [email protected] | [email protected] [email protected] | enabled | edit · delete |
Creating a forwarder
A three-step wizard: the source (username plus domain, previewed live as you type), the destinations (add as many rows as you need; each is validated as a real email address), and a final delivery-preference step, which also carries the loop warning: do not point two addresses at each other.
Rules the panel enforces: one forwarder per source address, at least one valid destination, and no forwarding an address to itself. The source cannot be changed later; to move a forwarder, delete and recreate it.
source destination1,destination2) written to the panel's isolated Postfix config, hashed with postmap and picked up by Postfix. Disabling a forwarder removes its line from the map, so the switch takes effect at the mail-server level, not just cosmetically. If the map cannot be written at creation time, the forwarder is rolled back rather than left half-applied. The same map carries the automatic postmaster/abuse/hostmaster role aliases and mailing list expansions.Managing forwarders
The table shows source, destinations as badges, type, creation date and a status switch that enables or disables the forwarder instantly, no confirmation needed. Edit changes the destination list and the enabled flag. Delete confirms first, then removes the forwarder and rewrites the map.
The summary cards at the top count total, active and destination addresses at a glance, and the search box filters by source or destination as you type.
Access
Forwarders require both the email and email_forwarding license features, and the endpoints are disabled when the server's local mail role is off. Visibility follows the roles and permissions chain (users their own, resellers their customers', ROOT all); the same CRUD is exposed over the External API with email:* scopes.