{"id":6143,"date":"2026-07-31T10:45:00","date_gmt":"2026-07-31T07:45:00","guid":{"rendered":"https:\/\/www.scalahosting.com\/kb\/?p=6143"},"modified":"2026-07-31T10:09:58","modified_gmt":"2026-07-31T07:09:58","slug":"forward-entire-domain-email","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/kb\/forward-entire-domain-email\/","title":{"rendered":"How to Forward All Email from One Domain to Another (Every Address, One Rule)"},"content":{"rendered":"\n

To forward every address on a domain to another domain in SPanel, open Email Forwarders<\/strong>, add a New Forwarder<\/strong>, set Forwarding Type<\/strong> to Forward an Entire Domain<\/strong>, choose the source under Forward from<\/strong>, enter the target under Forward to Domain(s)<\/strong>, and click Add Forwarder<\/strong>. One rule then mirrors the whole domain, so there’s no need for additional per-address setup. SPanel is unusual in keeping per-address, catch-all, and whole-domain forwarding together in one place.<\/p>\n\n\n\n

Domain-level forwarding matches each address to the same name on the destination automatically, and covers addresses you add later. It shares the Email Forwarders<\/strong> screen with per-address forwarders; the Forwarding Type<\/strong> selector switches between them. Per-address forwarders, the catch-all, and whole-domain forwarding do three different jobs – test a couple of real addresses after you save.<\/p>\n\n\n\n

When domain forwarding matters<\/strong><\/h2>\n\n\n\n

You changed domains. The company rebranded, or you bought a cleaner name, and everything old still points at the old mailbox – customers keep writing to orders@old-domain.com, and a supplier still has accounts@old-domain.com saved from years ago.<\/p>\n\n\n\n

The usual advice is to set up forwarders address by address. That works for two or three mailboxes. It falls apart at scale, and breaks the moment someone emails an address you forgot. What you want is one rule: everything for the old domain goes to the new domain, names unchanged. SPanel does that in a single form.<\/p>\n\n\n\n

The short version<\/strong><\/h2>\n\n\n\n

Whole-domain forwarding delivers every address on a source domain to the same-named address on a destination domain. It matches by pattern. Messages sent to info@old-domain.com are automatically forwarded to info@new-domain.com. Addresses you add later are covered too. In SPanel this is the Forward an Entire Domain<\/strong> type.<\/p>\n\n\n\n

What most people get wrong<\/strong><\/h2>\n\n\n\n

The common mistake is treating a catch-all as if it were domain forwarding. A catch-all collects mail sent to addresses that do not exist<\/em> on your domain – the salez@ when you only have sales@. It says nothing about where your real addresses go. Domain forwarding is the opposite: it sends every real address to its twin on another domain, name for name.<\/p>\n\n\n\n

A second mistake is assuming per-address forwarders and domain forwarding cancel out. They can coexist as separate solutions to two distinct problems.<\/p>\n\n\n\n

How it actually works<\/strong><\/h2>\n\n\n\n

Open the tool from the SPanel user area under Email Forwarders<\/strong>. A new account shows the empty state: “You haven’t created any Email forwarders yet.”<\/p>\n\n\n\n

\"How<\/figure>\n\n\n\n

To create a rule click New Forwarder<\/strong>. The first choice is Forwarding Type<\/strong>, with exactly two options: Forward an Email Address<\/strong> and Forward an Entire Domain<\/strong>. Pick the second, and the form adjusts.<\/p>\n\n\n\n

\"How<\/figure>\n\n\n\n

Now set Forward from<\/strong>, the source domain, and Forward to Domain(s)<\/strong>, the destination. Click Add Forwarder<\/strong> and the rule goes live. The single-address form differs, offering Forward to Email Address<\/strong> and a Pipe to a program<\/strong> option instead.<\/p>\n\n\n\n

Where SPanel is different<\/strong><\/h2>\n\n\n\n

SPanel keeps all three forwarding behaviors in one place. On the Email Forwarders<\/strong> screen you build a per-address redirect and, via the Forwarding Type<\/strong> switch, a whole-domain mirror. The catch-all sits nearby as a separate Default Address<\/strong> tool, keeping unmatched-mail handling distinct.<\/p>\n\n\n\n

The list view helps once you have a few rules: Domain<\/strong> and Type<\/strong> filters with Reset<\/strong> and Apply<\/strong>, columns including Forward to<\/strong> and Actions<\/strong>, and a Delete Selected<\/strong> control. SPanel is available on all ScalaHosting services at no extra cost.<\/p>\n\n\n\n

Practical example<\/strong><\/h2>\n\n\n\n

Think of a development agency that consolidates a client’s two brands under a single domain. To make the transition as smooth as possible, each brand keeps its public addresses, but staff need to use the inboxes associated with the newly-assigned primary domain. A whole-domain forward from the old brand mirrors every address in one rule without the need for dozens of hand-made redirects.<\/p>\n\n\n\n

Comparison: which forwarding tool fits<\/strong><\/h2>\n\n\n\n
Question<\/td>Per-address forwarder<\/td>Catch-all (Default Address)<\/td>Forward an Entire Domain<\/td><\/tr>
What it moves<\/td>One named address<\/td>Mail to non-existent addresses<\/td>Every address on the domain<\/td><\/tr>
Keeps the name on the other side<\/td>You choose the target<\/td>Sends to one chosen mailbox<\/td>Yes, name for name<\/td><\/tr>
Covers new addresses automatically<\/td>No<\/td>Yes (as unmatched mail)<\/td>Yes<\/td><\/tr>
Best for<\/td>A single redirect or a script pipe<\/td>A safety net for typos<\/td>A full domain move or brand mirror<\/td><\/tr>
Where in SPanel<\/td>Email Forwarders<\/td>Default Address tool<\/td>Email Forwarders<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Limitations and trade-offs<\/strong><\/h2>\n\n\n\n

Domain forwarding mirrors addresses; it does not move mailboxes. Mail is redirected to the destination, so the source account is not where messages come to rest once the rule is active. If you want copies kept on the source as well, that is a different setup – confirm your retention needs first.<\/p>\n\n\n\n

It also assumes matching names on both sides. If no support@ exists at the destination, that mail needs somewhere to go on the receiving domain, typically that domain’s own catch-all. Overlapping rules deserve a test too: if you keep a per-address forwarder or a catch-all alongside a domain-level rule, send a few real messages before trusting it.<\/p>\n\n\n\n

How you should approach domain forwarding<\/strong><\/h2>\n\n\n\n

List the addresses that receive mail today, so you have something to test against. Create the rule, set Forward from<\/strong> and Forward to Domain(s)<\/strong>, and save with Add Forwarder<\/strong>. Send test messages to your busiest addresses and confirm they arrive before retiring any old per-address forwarders you no longer need.<\/p>\n\n\n\n

Step-by-step<\/strong><\/h2>\n\n\n\n
    \n
  1. From the SPanel user area, open Email Forwarders<\/strong>.<\/li>\n\n\n\n
  2. In the New Forwarder<\/strong> panel, set Forwarding Type<\/strong> to Forward an Entire Domain<\/strong>.<\/li>\n\n\n\n
  3. Choose the source domain under Forward from<\/strong>.<\/li>\n\n\n\n
  4. Enter the destination under Forward to Domain(s)<\/strong>.<\/li>\n\n\n\n
  5. Click Add Forwarder<\/strong> to create the rule.<\/li>\n\n\n\n
  6. In the Email Forwarders<\/strong> list, filter by Type<\/strong> and click Apply<\/strong> to confirm the new rule appears, with its destination under Forward to<\/strong>.<\/li>\n<\/ol>\n\n\n\n

    FAQ<\/strong><\/h2>\n\n\n\n

    Q:<\/strong> What is the difference between a catch-all and forwarding an entire domain?<\/strong><\/p>\n\n\n\n

    A:<\/strong> A catch-all receives only mail sent to addresses that do not exist on your domain, and delivers it to one chosen mailbox. Forwarding an entire domain is the opposite: it takes every real address and sends each to its match on another domain, name for name.<\/p>\n\n\n\n

    Q:<\/strong> Do I need to set up each address separately?<\/strong><\/p>\n\n\n\n

    A:<\/strong> No. That is the point of the Forward an Entire Domain<\/strong> type in SPanel. One rule covers every address on the source domain, and it keeps working for addresses you add later, because it matches by pattern rather than from a fixed list.<\/p>\n\n\n\n

    Q:<\/strong> Will info@old-domain reach info@new-domain automatically?<\/strong><\/p>\n\n\n\n

    A:<\/strong> Yes. Domain-level forwarding preserves the part before the @ and changes only the domain, so info@old-domain is delivered to info@new-domain, sales@ to sales@, and so on across every address. You never name the individual addresses one by one, and any you add later are carried by the same rule.<\/p>\n\n\n\n

    Q:<\/strong> Can I still use per-address forwarders at the same time?<\/strong><\/p>\n\n\n\n

    A:<\/strong> Yes. SPanel keeps per-address forwarders, the catch-all, and whole-domain forwarding as separate tools that coexist. If you run more than one rule that could match the same address, send test messages and confirm the result before relying on it in production.<\/p>\n\n\n\n

    Q:<\/strong> Where do I find domain forwarding in SPanel?<\/strong><\/p>\n\n\n\n

    A:<\/strong> It’s in SPanel’s User interface at Home > Email Forwarders. Add a New Forwarder<\/strong> and set the Forwarding Type<\/strong> to Forward an Entire Domain<\/strong>. The catch-all is a separate tool, the Default Address<\/strong>.<\/p>\n\n\n\n

    Q:<\/strong> What happens if the destination domain has no matching address?<\/strong><\/p>\n\n\n\n

    A:<\/strong> Whole-domain forwarding does not create addresses on the destination. If mail arrives for a name that does not exist there, it needs somewhere to go on the receiving side – usually that domain’s own catch-all. Set the destination up to receive the names you expect first.<\/p>\n\n\n\n