{"id":74891,"date":"2026-08-21T02:06:44","date_gmt":"2026-08-21T08:06:44","guid":{"rendered":"https:\/\/www.scalahosting.com\/blog\/?p=74891"},"modified":"2026-08-21T02:06:45","modified_gmt":"2026-08-21T08:06:45","slug":"email-forwarder-vs-catch-all","status":"publish","type":"post","link":"https:\/\/www.scalahosting.com\/blog\/email-forwarder-vs-catch-all\/","title":{"rendered":"Email Forwarders vs. Catch-All vs. Domain Forwarding: Which One Do You Need?"},"content":{"rendered":"\n<div class=\"wp-block-group alert-green\"><div class=\"wp-block-group__inner-container is-layout-constrained wp-block-group-is-layout-constrained\">\n<p class=\"wp-block-paragraph\"><strong>TL;DR<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An email forwarder redirects one specific address to another mailbox. A catch-all collects every message sent to an address that doesn\u2019t exist on your domain, so nothing bounces. Whole-domain forwarding mirrors every address on a domain to the matching mailbox on one or more destination domains &#8211; info@old-domain reaches info@new-domain &#8211; with no per-address setup.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In SPanel, forwarders and whole-domain forwarding both can be found under Email Forwarders, while the catch-all is a separate Default Address tool.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use a <strong>per-address forwarder<\/strong> for one address, like sales@, landing in an existing inbox.<\/li>\n\n\n\n<li>Use a <strong>catch-all<\/strong> so mail to typo\u2019d or guessed addresses doesn\u2019t fail.<\/li>\n\n\n\n<li>Use <strong>whole-domain forwarding<\/strong> after a rebrand so every address maps across automatically.<\/li>\n\n\n\n<li>SPanel\u2019s <strong>Forward an Entire Domain<\/strong> option needs no address-by-address setup.<\/li>\n\n\n\n<li><strong>None of the three is a mailbox<\/strong> &#8211; forwarded mail still needs a real place to land.<\/li>\n<\/ul>\n<\/div><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">You rebranded. The old domain still gets real mail &#8211; invoices to accounts@, a customer who saved sales@ two years ago. Every one of those messages that bounces is an inconvenience, to say the least. Three different tools can route that mail in SPanel, and they\u2019re easy to confuse. Pick the wrong one, and you either miss messages or drown in spam.\u00a0<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This guide explains what each does, what it doesn\u2019t do, and how to set the right one up in SPanel.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Three tools, three jobs<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A <strong>forwarder<\/strong> is surgical: one source address, one or more destinations. A <strong>catch-all<\/strong> is a safety net that grabs anything addressed to your domain with no mailbox of its own. <strong>Whole-domain forwarding<\/strong> is a mirror &#8211; it copies the entire address space of one domain onto another.&nbsp;<\/p>\n\n\n\n<p class=\"alert-blue wp-block-paragraph\"><strong>IMPORTANT:<\/strong> \u201cDomain forwarding\u201d here means a whole domain\u2019s email, address for address, not a website URL redirect. The diagram below shows how each one moves mail.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large mpg-gallery\"><img decoding=\"async\" width=\"1140\" height=\"509\" src=\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/email-routing-types-diagram-1140x509.webp\" alt=\"Email Forwarders vs. Catch-All vs. Domain Forwarding: Which One Do You Need?, Three tools, three jobs\" class=\"wp-image-74892\" srcset=\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/email-routing-types-diagram-1140x509.webp 1140w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/email-routing-types-diagram-300x134.webp 300w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/email-routing-types-diagram-768x343.webp 768w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/email-routing-types-diagram-1536x686.webp 1536w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/email-routing-types-diagram.webp 1903w\" sizes=\"(max-width: 361px) 660px, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 910px, 1140px\" \/><figcaption class=\"wp-element-caption\"><em>How the three routing types move your mail: one-to-one, many-to-one, and address-for-address mirroring.<\/em><\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>The Two Mistakes That Can Lose Your Emails<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The first mistake is <strong>treating a catch-all as smart routing<\/strong>. It isn\u2019t selective &#8211; it sweeps up mail to sales@, to saels@, and to whatever a spam bot invents, then dumps it all in one place. On an aging domain, that inbox fills with junk fast.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The second mistake is <strong>reaching for individual forwarders after a rebrand<\/strong>. If your old domain has 15 live addresses, that\u2019s 15 fragile, hand-built rules &#8211; and it\u2019s easy to forget one. Whole-domain forwarding covers that case with a single rule.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How Each Mail Routing Type Behaves<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A per-address forwarder matches one exact recipient and hands the message to another address.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A catch-all, called the <strong>Default Address<\/strong> in SPanel, defines what happens to mail that matches no mailbox and no forwarder on your domain. You point it at one destination, and every unmatched message goes there &#8211; or you discard unmatched mail to cut spam.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Whole-domain forwarding takes a source domain and one or more destination domains. For every address it delivers to the same local part on the destination &#8211; info@ to info@, billing@ to billing@ &#8211; all at once. You never list the addresses; the rule derives them from what arrives.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Both Forwarder Types On One SPanel Screen<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Here\u2019s where <a href=\"https:\/\/www.scalahosting.com\/spanel.html\">SPanel<\/a> does things its own way.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Both per-address and whole-domain forwarding can be found on a single screen. Open the user area and go to <strong>Email Forwarders<\/strong>. The <strong>New Forwarder<\/strong> panel opens with a <strong>Forwarding Type<\/strong> choice offering exactly two options: <em>Forward an Email Address<\/em> and <em>Forward an Entire Domain<\/em>.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large mpg-gallery\"><img decoding=\"async\" width=\"1140\" height=\"453\" src=\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/spanel-new-forwarder-panel-1140x453.webp\" alt=\"Email Forwarders vs. Catch-All vs. Domain Forwarding: Which One Do You Need?, Both Forwarder Types On One SPanel Screen\" class=\"wp-image-74893\" srcset=\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/spanel-new-forwarder-panel-1140x453.webp 1140w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/spanel-new-forwarder-panel-300x119.webp 300w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/spanel-new-forwarder-panel-768x305.webp 768w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/spanel-new-forwarder-panel-1536x610.webp 1536w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/spanel-new-forwarder-panel.webp 1643w\" sizes=\"(max-width: 361px) 660px, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 910px, 1140px\" \/><figcaption class=\"wp-element-caption\"><em>Illustration of the New Forwarder panel &#8211; one Forwarding Type toggle switches between address-level and domain-level forwarding.<\/em><\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Pick <strong>Forward an Email Address,<\/strong> and you get a Forward from source selector, a Forward to Email Address field, and a Pipe to a program option. Pick <strong>Forward an Entire Domain<\/strong> and the destination field becomes Forward to Domain(s), the target for the whole-domain mirror.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Add Forwarder button commits either type, and the list below shows what you\u2019ve created with <strong>Domain <\/strong>and <strong>Type <\/strong>filters, a <strong>Forward to<\/strong> column, an <strong>Actions <\/strong>column, and <strong>Delete Selected<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That single-toggle design makes a real difference.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Some setups scatter address forwarding and domain forwarding across separate screens &#8211; or push the whole-domain case down to config-file edits. Keeping both behind one control means a rebrand doesn\u2019t send you hunting through menus. It\u2019s included for free on every <a href=\"https:\/\/www.scalahosting.com\/managed-cloud-hosting.html\">managed VPS<\/a> plan, built and maintained in-house rather than licensed in.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you\u2019re weighing control panels, the <a href=\"https:\/\/www.scalahosting.com\/blog\/spanel-vs-cpanel\/\">SPanel vs. cPanel comparison<\/a> covers the wider feature and cost picture.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Forwarder vs. Catch-all vs. Whole-domain &#8211; Side by Side Comparison<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If you only read one section, read this. The table lines up all three routing types across the questions that actually decide which one you need.<\/p>\n\n\n\n<figure class=\"wp-block-table is-style-regular green-rows\"><table class=\"has-fixed-layout\"><thead><tr><th><\/th><th><strong>Per-address forwarder<\/strong><\/th><th><strong>Catch-all (Default Address)<\/strong><\/th><th><strong>Whole-domain forwarding<\/strong><\/th><\/tr><\/thead><tbody><tr><td>What it matches<\/td><td>One exact address<\/td><td>Mail with no matching mailbox or forwarder<\/td><td>Every address on the source domain<\/td><\/tr><tr><td>Where you set it<\/td><td>Email Forwarders \u2192 Forward an Email Address<\/td><td>Default Address tool<\/td><td>Email Forwarders \u2192 Forward an Entire Domain<\/td><\/tr><tr><td>Destination<\/td><td>An address (or piped program)<\/td><td>One destination for all unmatched mail<\/td><td>One or more domains, mapped address-for-address<\/td><\/tr><tr><td>Best for<\/td><td>Redirecting a single address<\/td><td>Not losing mail to unknown addresses<\/td><td>Rebrands, mergers, domain moves<\/td><\/tr><tr><td>Main risk<\/td><td>Forgetting an address<\/td><td>Collecting spam<\/td><td>Mirroring unwanted addresses too<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Two Real Setups &#8211; Practical Example<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Joe runs a small ecommerce store in Atlanta with one domain and wants replies to orders@ in his personal inbox without a second login. A single <strong>Forward an Email Address<\/strong> rule does it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A digital agency migrates a client from oldbrand.com to newbrand.com, where dozens of staff addresses exist. Rather than recreate each one, they set <strong>Forward an Entire Domain<\/strong> with the new domain as the target, and every address maps across on day one. A Default Address catch-all on the old domain then catches mail to any since-deleted address.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What None of These Can Do<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">None of these three email forwarding methods is a mailbox. A forwarder with no valid destination sends mail into a dead end, so the receiving address must exist and stay active.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A catch-all is a magnet for spam: point it at a person\u2019s inbox on an aging domain, and you hand them a firehose, which is why many teams route it to a low-priority address or discard unmatched mail. Whole-domain forwarding has the mirror-image flaw &#8211; it copies every address, including ones you\u2019d rather retire.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Rules can also overlap.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A whole-domain rule, a per-address forwarder, and a catch-all could all lay claim to the same incoming message, and the order SPanel applies them in decides where that mail ends up. If your setup depends on that precedence &#8211; say, one address that must override the domain-wide mirror &#8211; confirm the exact order with our support team before you rely on it. The same goes for large fan-outs: the Forward to Domain(s) field accepts more than one target, but check the supported ceiling with support before building a rule that leans on a high number of destinations.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Which Email Forwarding Method to Pick<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Start narrow and widen only as needed.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Need one address redirected?<\/em> Build one forwarder and stop. <em>Moving a whole domain?<\/em> Use Forward an Entire Domain instead of a pile of individual rules. Add a catch-all last, and only if unmatched mail is worth catching. Review the Email Forwarders list periodically and prune rules pointing at dead addresses. When you\u2019re not sure, walk the quick decision tree below.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large mpg-gallery\"><img decoding=\"async\" width=\"1140\" height=\"786\" src=\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/email-routing-decision-flow-1140x786.webp\" alt=\"Email Forwarders vs. Catch-All vs. Domain Forwarding: Which One Do You Need?, Which Email Forwarding Method to Pick\" class=\"wp-image-74894\" srcset=\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/email-routing-decision-flow-1140x786.webp 1140w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/email-routing-decision-flow-300x207.webp 300w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/email-routing-decision-flow-768x530.webp 768w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/email-routing-decision-flow-1536x1059.webp 1536w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/email-routing-decision-flow.webp 1972w\" sizes=\"(max-width: 361px) 660px, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 910px, 1140px\" \/><figcaption class=\"wp-element-caption\"><em>A quick decision path from \u201cwhat am I trying to route?\u201d to the right SPanel tool.<\/em><\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Set up Whole-domain Forwarding in SPanel<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Whole-domain forwarding is the rule most people reach for after a rebrand. Here\u2019s the full sequence. You start on the empty <strong>Email Forwarders<\/strong> screen shown below.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large mpg-gallery\"><img decoding=\"async\" width=\"1140\" height=\"755\" src=\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/spanel-email-forwarders-empty-state-1140x755.webp\" alt=\"Email Forwarders vs. Catch-All vs. Domain Forwarding: Which One Do You Need?, Set up Whole-domain Forwarding in SPanel\" class=\"wp-image-74895\" srcset=\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/spanel-email-forwarders-empty-state-1140x755.webp 1140w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/spanel-email-forwarders-empty-state-300x199.webp 300w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/spanel-email-forwarders-empty-state-768x509.webp 768w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/spanel-email-forwarders-empty-state-1536x1018.webp 1536w, https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2026\/08\/spanel-email-forwarders-empty-state.webp 1600w\" sizes=\"(max-width: 361px) 660px, (max-width: 767px) 89vw, (max-width: 1000px) 54vw, (max-width: 1071px) 910px, 1140px\" \/><figcaption class=\"wp-element-caption\"><em>The Email Forwarders screen before any rules exist &#8211; your starting point.<\/em><\/figcaption><\/figure>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Log in to SPanel<\/strong> and open the user area.<\/li>\n\n\n\n<li><strong>Go to Email Forwarders.<\/strong> The breadcrumb reads Home \u203a Email Forwarders.<\/li>\n\n\n\n<li><strong>Open the New Forwarder panel<\/strong> and find the Forwarding Type choice.<\/li>\n\n\n\n<li><strong>Select Forward an Entire Domain.<\/strong><\/li>\n\n\n\n<li><strong>Choose the source domain<\/strong> in the Forward from selector.<\/li>\n\n\n\n<li><strong>Enter the target<\/strong> in the Forward to Domain(s) field.<\/li>\n\n\n\n<li><strong>Click Add Forwarder<\/strong> to create the rule.<\/li>\n\n\n\n<li><strong>Confirm the rule appears<\/strong> in the Email Forwarders list; filter by Domain and Type if the list is long.<\/li>\n<\/ol>\n\n\n\n<p class=\"alert-blue wp-block-paragraph\"><strong>Before you rely on it: <\/strong>make sure the matching mailboxes already exist on the destination domain. Whole-domain forwarding routes mail to the same address on the target, but it doesn\u2019t create those inboxes &#8211; if info@ doesn\u2019t exist on the destination, forwarded mail for info@ has nowhere to land.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Related resources<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Weighing a forward against a full inbox? Our guide to <a href=\"https:\/\/www.scalahosting.com\/blog\/how-to-migrate-your-email-to-a-new-hosting-provider\/\">migrating email accounts in SPanel<\/a> covers the mailbox side. You can also check out our <a href=\"https:\/\/www.scalahosting.com\/blog\/website-migration\/\">full website migration checklist<\/a> to ensure you are not missing any vital steps.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">SPanel is an innovative hosting management platform actively driven by its users. You can <a href=\"https:\/\/features.spanel.io\/\">suggest and vote for new SPanel features<\/a>, and our Development Team will make sure you find them in the next update releases.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Frequently Asked Questions<\/strong><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>What is the difference between an email forwarder and a catch-all?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> A forwarder targets one exact address you choose and redirects it to a destination. A catch-all targets everything else &#8211; any message sent to your domain with no matching mailbox or forwarder. Forwarders route mail you expect; a catch-all grabs whatever is left over, including mail to addresses you never set up.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>Does whole-domain forwarding create mailboxes on the new domain?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> No. It routes mail to the matching address on the destination domain, but that address still needs a real mailbox or its own forwarder waiting for it. If info@ doesn\u2019t exist on the destination, forwarded mail for info@ has nowhere to land. Set up the receiving side first.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>Where do I set up a catch-all in SPanel?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> The catch-all is handled by the Default Address tool in the email section, which is separate from the Email Forwarders screen. Per-address forwarders and whole-domain forwarding both live under Email Forwarders; the catch-all for unmatched mail is configured on its own in your SPanel email area.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>Can one rule forward a domain to more than one destination?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> Yes. Whole-domain forwarding uses a Forward to Domain(s) field, which is written to accept more than one destination. There\u2019s a practical ceiling on how many, so if you need a wide fan-out, confirm the supported number with our support team before you build the rule. For a one-to-one domain move, a single destination is all you need.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>Is email forwarding the same as forwarding my website\u2019s domain?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> No. Everything here is about email routing between addresses and domains. Pointing a website\u2019s URL elsewhere is a separate DNS and web-server task, not something the Email Forwarders screen controls. If someone says \u201cforward the domain,\u201d clarify whether they mean the email or the website.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Q:<\/strong> <strong>How do I remove a forwarder I no longer need?<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>A:<\/strong> Open the Email Forwarders list, find the rule with the Domain and Type filters, and use the Actions column &#8211; or select several rules and use Delete Selected. Removing a forwarder stops the redirect immediately, so make sure any mail flowing through it has another path first.<\/p>\n\n\n\n<script type=\"application\/ld+json\">\n    {\n      \"@context\": \"https:\/\/schema.org\",\n      \"@type\": \"FAQPage\",\n      \"mainEntity\": [{\n        \"@type\": \"Question\",\n        \"name\": \"What is the difference between an email forwarder and a catch-all?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"A forwarder targets one exact address you choose and redirects it to a destination. A catch-all targets everything else - any message sent to your domain with no matching mailbox or forwarder. Forwarders route mail you expect; a catch-all grabs whatever is left over, including mail to addresses you never set up.\"\n        }\n      }, {\n        \"@type\": \"Question\",\n        \"name\": \"Does whole-domain forwarding create mailboxes on the new domain?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"No. It routes mail to the matching address on the destination domain, but that address still needs a real mailbox or its own forwarder waiting for it. If info@ doesn\u2019t exist on the destination, forwarded mail for info@ has nowhere to land. Set up the receiving side first.\"\n        }\n      },{\n        \"@type\": \"Question\",\n        \"name\": \"Where do I set up a catch-all in SPanel?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"The catch-all is handled by the Default Address tool in the email section, which is separate from the Email Forwarders screen. Per-address forwarders and whole-domain forwarding both live under Email Forwarders; the catch-all for unmatched mail is configured on its own in your SPanel email area.\"\n        }\n      },{\n        \"@type\": \"Question\",\n        \"name\": \"Can one rule forward a domain to more than one destination?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Yes. Whole-domain forwarding uses a Forward to Domain(s) field, which is written to accept more than one destination. There\u2019s a practical ceiling on how many, so if you need a wide fan-out, confirm the supported number with our support team before you build the rule. For a one-to-one domain move, a single destination is all you need.\"\n        }\n      },{\n        \"@type\": \"Question\",\n        \"name\": \"Is email forwarding the same as forwarding my website\u2019s domain?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"No. Everything here is about email routing between addresses and domains. Pointing a website\u2019s URL elsewhere is a separate DNS and web-server task, not something the Email Forwarders screen controls. If someone says \u201cforward the domain,\u201d clarify whether they mean the email or the website.\"\n        }\n      },{\n        \"@type\": \"Question\",\n        \"name\": \"How do I remove a forwarder I no longer need?\",\n        \"acceptedAnswer\": {\n          \"@type\": \"Answer\",\n          \"text\": \"Open the Email Forwarders list, find the rule with the Domain and Type filters, and use the Actions column - or select several rules and use Delete Selected. Removing a forwarder stops the redirect immediately, so make sure any mail flowing through it has another path first.\"\n        }\n      }]\n    }\n<\/script>\n","protected":false},"excerpt":{"rendered":"<p>TL;DR An email forwarder redirects one specific address to another mailbox. A catch-all collects every message sent to an address &#8230;<\/p>\n","protected":false},"author":106,"featured_media":74898,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_seopress_titles_title":"Forwarder vs. Catch-All vs. Domain Forwarding %%sep%% %%sitetitle%%","_seopress_titles_desc":"Email forwarder, catch-all, or whole-domain forwarding? See what each does in SPanel, when to use it, and how to set the right one up.","_seopress_robots_index":"","_seopress_robots_follow":"","_seopress_robots_imageindex":"","_seopress_robots_snippet":"","_seopress_robots_primary_cat":"","_seopress_robots_breadcrumbs":"","_seopress_robots_freeze_modified_date":"","_seopress_robots_custom_modified_date":"","_seopress_robots_canonical":"","_seopress_social_fb_title":"","_seopress_social_fb_desc":"","_seopress_social_fb_img":"","_seopress_social_fb_img_attachment_id":0,"_seopress_social_fb_img_width":0,"_seopress_social_fb_img_height":0,"_seopress_social_twitter_title":"","_seopress_social_twitter_desc":"","_seopress_social_twitter_img":"","_seopress_social_twitter_img_attachment_id":0,"_seopress_social_twitter_img_width":0,"_seopress_social_twitter_img_height":0,"_seopress_redirections_value":"","_seopress_redirections_enabled":"","_seopress_redirections_enabled_regex":"","_seopress_redirections_logged_status":"","_seopress_redirections_param":"","_seopress_redirections_type":0,"_seopress_analysis_target_kw":"","_seopress_news_disabled":"","_seopress_video_disabled":"","_seopress_video":[],"_seopress_pro_schemas_manual":[],"_seopress_pro_rich_snippets_disable_all":"","_seopress_pro_rich_snippets_disable":[],"_seopress_pro_schemas":[],"footnotes":""},"categories":[123],"tags":[],"class_list":["post-74891","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-email-hosting"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/posts\/74891","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/users\/106"}],"replies":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/comments?post=74891"}],"version-history":[{"count":3,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/posts\/74891\/revisions"}],"predecessor-version":[{"id":74900,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/posts\/74891\/revisions\/74900"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/media\/74898"}],"wp:attachment":[{"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/media?parent=74891"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/categories?post=74891"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.scalahosting.com\/blog\/wp-json\/wp\/v2\/tags?post=74891"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}