Email Forwarding: How to Set It Up in cPanel, Gmail, Outlook

What is email forwarding and how does it work?

Email forwarding is the automatic delivery of a message sent to one address to another address. The mail server or mail service receives the message, checks your rule and sends a copy to the destination. For example, every message to info@example.com can land in your personal inbox.

We wrote this guide for website and online store owners, and for developers who manage their own cPanel account or VPS. We are a digital marketing and web team, not a hosting company. So we based every step on cPanel, Google and Microsoft help pages and on IETF standards. We left out any setting we could not confirm.

Forwarding looks simple, but two different servers take part. The first one receives the message from the sender. The second one belongs to the address you forward to. Most problems come from the authentication check between those two servers.

That is why we split the guide into three parts. First, we show how to set up forwarding in cPanel, Gmail and Outlook. Then we explain why delivery sometimes fails. Finally, we cover the alternatives and the jobs you should leave to your provider.

What is the difference between email forwarding, an alias, a shared mailbox and a copy?

People mix up these four terms because each one gets a message to someone. Their logic differs, though. Forwarding sends the message to another server. An alias is a second name for the same mailbox. A shared mailbox lets several people open one inbox.

Read the table like this: if the message can stay in one mailbox you control, an alias or shared mailbox is safer. If you have to move to another provider, you need a forwarder.

When should you use email forwarding?

Forwarding works well during transitions and in simple setups. However, you should know its side effects before you build a permanent system on it.

• You changed your domain or brand and want the old address to keep working for a while.
• An employee left and you want to route their mail to a manager for a short period.
• You want to connect the contact address on your site to one personal inbox.
• You want to spread sales and support addresses across a small team.

On the other hand, high-volume or sensitive mail deserves a real mailbox. A forwarded message can lose some of its authentication, so it may end up in the spam folder.

How do you add an email forwarder in cPanel?

According to the official cPanel documentation, adding a forwarder takes a few steps. Menu names can differ slightly between interface versions, but the logic stays the same.

1. Log in to cPanel and open Forwarders in the Email section.
2. Pick the right domain from the Managing menu.
3. Click Add Forwarder in the Create an Email Account Forwarder section.
4. Type the part before the @ sign in the Address to forward field, for example info.
5. Choose the domain from the Domain menu.
6. Select Forward to Email Address and type the destination.
7. Save, then send yourself a test message from an outside account.

The documentation says you can enter several destination addresses separated by commas. So one address can reach several people. Keep in mind that every extra destination adds one more spam filter that can block the message.

After you save, the forwarder shows up in the list. To change the destination, delete the forwarder and create it again. Deleting does not touch old messages, and it only stops new ones. So add the new forwarder first, then remove the old one, and you avoid a gap.

What do the advanced cPanel forwarding options mean?

The forwarder screen offers a few options besides Forward to Email Address. Most site owners never need them.

• Discard and send an error to the sender (at SMTP time): This rejects the message and returns an error to the sender. You can keep the default text or write your own.
• Forward to a system account: This passes the message to a system user on the server. Use it only if you know exactly what you are doing.
• Discard (Not Recommended): This silently deletes the message without telling the sender. cPanel advises against it because an important message can vanish.
• Pipe to a Program: This hands the message to a script. A badly written script loses mail or opens a security hole.

In practice the first option is enough. If your setup needs a script or a system account, leave it to your hosting provider or system administrator.

What does a cPanel domain forwarder do?

A domain forwarder works for a whole domain instead of a single address. The cPanel documentation calls this section Forward All Email for a Domain. You click Add Domain Forwarder, then choose the source domain and the destination domain.

According to the documentation, this rule applies when the normal addresses do not exist. In other words, existing mailboxes keep working, and addresses that do not exist go to the destination domain. We cover the sibling idea, the catch-all address, in a separate article, so we will not repeat it here.

The rule has one side effect: spam sent to random or wrong addresses flows to the destination too. So we suggest using domain-level forwarding only during a transition, and only while you watch the result.

How do you set up automatic email forwarding in Gmail?

The Gmail help page gives the steps clearly. First you add the destination address. Then that address confirms through a verification link. Finally you turn forwarding on.

1. In Gmail, click the gear icon and open See all settings.
2. Switch to the Forwarding and POP/IMAP tab.
3. Click Add a forwarding address and type the destination.
4. Click the verification link that arrives at the destination.
5. Go back to settings and select Forward a copy of incoming mail to.
6. Choose whether Gmail keeps, archives or deletes its copy, then click Save Changes.

According to Google, Gmail forwards all new messages except spam. To forward only certain messages, turn automatic forwarding off. Then create a filter from the search box and choose the Forward it action.

Google also says Gmail shows a forwarding notice in your inbox for one week. That reminder helps you notice if someone adds a rule to your account without permission.

How do you forward email in Outlook with a rule?

Microsoft's support page says the steps are similar in Outlook on the web, the new Outlook and classic Outlook. You follow Settings, Mail, Rules, create a new rule and give it a name.

Set the condition to Apply to all messages. Then pick Forward to or Redirect to as the action and type the recipient. Finally, save the rule.

The difference between the two actions matters. According to Microsoft, Forward to makes the message appear to come from you, and replies go to your forwarding address. Redirect to keeps the original sender, so replies go straight back to that person. For customer mail, Redirect to is often the better fit. Still, your company policy or administrator may restrict forwarding to outside addresses.

Microsoft also notes that copies stay in your mailbox. If the mailbox reaches its limit, the rule may stop working. So clean the mailbox regularly.

Why does email forwarding break SPF, DKIM and DMARC?

SPF lists in your domain's DNS record which servers may send mail for that domain. The receiving server looks at the IP address of the server that delivers the message. In forwarding, that server is no longer the original sender's server. It is the server you forward through.

As a result, the receiver cannot find your server's IP address in the original domain's SPF record. SPF fails. RFC 7208 defines SPF.

DKIM works differently. The sending server signs the message, and the signature covers certain headers and the body. If the message passes through unchanged, the signature stays valid. However, if the forwarder adds a subject tag or a footer, the signature breaks.

DMARC combines the two. At least one of SPF or DKIM must pass, and the passing identity must align with the visible From domain. RFC 7489 defines this alignment. Because SPF fails in forwarding, DKIM usually decides the result.

In short, the fate of a forwarded message depends on whether the sender's DKIM signature survives. If the sender does not use DKIM and relies only on SPF, the forwarded message cannot pass DMARC. You may not notice at first, because the message often arrives but lands in spam.

When does a forwarded message get rejected?

If the sender's domain has a DMARC policy of reject, and the forwarded message fails both SPF and DKIM alignment, the receiving server may reject it. With a quarantine policy, the message goes to spam. With a none policy, the sender asks for no special action.

RFC 7489 admits that mail flows can get complicated because of forwarding and similar causes. So it lets receivers deviate from the published policy. Still, not every receiver shows the same tolerance. If something goes wrong when you forward to Gmail or Outlook, this is often the reason.

For example, a bank or a large brand has a strict DMARC policy, so mail from it may be rejected after forwarding. A message from a small local business usually passes without trouble.

That is why you should not judge forwarding by your own test message alone. Try messages from different senders as well.

What are SRS and ARC, and how do they repair forwarding?

SRS (Sender Rewriting Scheme) is a technique where the forwarding server rewrites the envelope sender with its own domain. The SPF check then runs against the forwarder's own record and passes. The original address is encoded inside the rewritten one. SRS is a widely used practice, not a single RFC standard.

ARC (Authenticated Received Chain) takes another route. According to RFC 8617, ARC lets intermediate servers record the authentication results they saw when the message arrived. It does this in a chain, using three headers: ARC-Authentication-Results, ARC-Message-Signature and ARC-Seal.

If the receiver trusts the chain, it can accept the message even though SPF and DKIM broke along the way. However, RFC 8617 has Experimental status, and not every receiver gives ARC the same weight.

You do not set these up yourself. The provider that runs the mail server configures them. Your job is to ask the provider whether they support SRS.

Why do forwarded emails land in the spam folder?

Forwarded messages land in spam for two main reasons. The first is weak authentication. The second is the reputation of the forwarding server. If a shared server forwards a lot of spam, its IP reputation drops, and clean messages suffer too.

That is why blindly forwarding the spam sent to your domain does harm. If the destination provider marks most of what your server sends as spam, your real messages get caught by the same filter.

These steps lower the risk:

• Run the spam filter on the server before forwarding, so spam never reaches the destination.
• Mark forwarded messages as not spam in the destination mailbox.
• Delete forwarders you no longer need.
• Use a real mailbox instead of forwarding where you can, and connect with POP or IMAP.

Spam filter settings live in your hosting panel or with your provider's support team. If you do not see the option, ask them.

Do not forget the receiving side either. The destination provider may judge forwarded messages more strictly in the first weeks. Over time, as clean and regular mail arrives, that strictness usually eases. During that period, marking forwarded messages as not spam by hand helps.

How does an email forwarding loop start, and how do you prevent it?

A loop means a message keeps bouncing between two addresses. The classic example is forwarding address A to B and address B back to A. Mail servers usually count how many times a message changed hands and reject it once it passes a limit. Even so, mailboxes can fill up in the meantime.

Loops usually start in these situations:

• You forward Gmail to an address that forwards back to you.
• A cPanel forwarder points to the account's own address.
• A domain forwarder and a single-address forwarder trigger each other.

To prevent them, draw your forwarding map on paper or in a spreadsheet. Make sure each address goes in only one direction. Also send a test message after every change and watch the inboxes.

Is email forwarding the same as website redirection?

No. Email forwarding moves mail messages and relates to MX records. Website redirection (301 or 302) sends a visitor's browser from one URL to another and runs over HTTP. They are separate systems, and one does not affect the other.

When you move a domain, you need to think about both. For web traffic, you set up 301 redirects and check for redirect chains. For email, you move the MX records and the forwarders.

To understand chain errors on the web side, read our redirect chain guide. To see where your URLs go, use our redirect checker.

When is an alias or shared mailbox better than forwarding?

In setups that stay under one domain, you often do not need forwarding at all. Because the message never moves to another server, no SPF or DKIM problem appears.

An alias is an extra name for the same mailbox. For example, support@example.com and info@example.com can land in one inbox. Alias support depends on your mail service. Google Workspace, Microsoft 365 and many hosting panels offer it, but check the details with your provider.

A shared mailbox suits teamwork. Several people open the same inbox, see who answered, and avoid double replies.

Let us run an example calculation. Say a five-person store team has an info@ address, and every message goes to all five people. The same message sits in five mailboxes, nobody knows whether it was answered, and two people sometimes reply to the same customer. In a shared mailbox, the message stays in one place and its status is visible. This is a made-up scenario, and the numbers belong to the story only.

To choose a mail setup, read our business email guide for custom domains. It also covers the decision between hosting mail and a cloud mail service.

How does an MX record affect email forwarding?

An MX (Mail Exchanger) record tells the world which server receives mail for your domain. A forwarder only works on that server. If the MX record points to another service, the forwarder you created in cPanel never runs, because the message never reaches the cPanel server.

This often happens on sites that use Google Workspace or Microsoft 365 but left a forwarder in the old hosting account. The forwarder looks fine, yet nothing processes it, since mail goes elsewhere.

So query the MX record first, then set up the forwarder in the system that the record points to. Be careful when you change an MX record, because it directly changes mail flow. A wrong change can make messages vanish for hours. If you are unsure, make the change together with your provider.

How do you plan email forwarding when you move a domain?

People often forget email when they change a domain or a host. Yet if mail stops while the website opens on the new server, customer messages can disappear. The order below reduces the risk.

1. Write all mailboxes and forwarders from the old system in a table.
2. Create the same mailboxes and forwarders on the new system in advance.
3. Move mailbox contents with IMAP or with the provider's transfer tool.
4. Change the MX records with a low TTL and wait for them to spread.
5. Watch both systems for a few days, then close the old one.

During the move, the old and new servers work together for a while. So watch out for forwarding loops. When you forward the old address to the new one, check that the new one does not forward back.

Before you close anything, back up all mailboxes. That way you can go back if something is missing after the move.

What are the most common email forwarding mistakes?

Common problems usually come from simple causes. The list below shows what to check before you start.

• You mistype the destination address, and the messages go nowhere.
• A cPanel forwarder exists while the MX record points to another server.
• The spam filter stays off, so all the junk pours into the destination mailbox.
• Nobody writes down the forwarding map, and a loop appears.
• A former employee's forwarding stays open forever.
• Testing happens only from the same provider, so the real behavior stays hidden.

A two-minute checklist prevents most of these mistakes. After setup, also check the destination spam folder for a week.

How do you test that forwarding works?

First, send a test message from an address at another provider to the address you forward. Then check the inbox and the spam folder of the destination. When the message arrives, open the headers and read the authentication results.

The headers contain an Authentication-Results line. It shows the SPF, DKIM and DMARC results. It also shows how the sender name appears and which servers carried the message.

To see the MX record from the DNS side, you can run these commands:

dig +short MX example.com
dig +short TXT example.com

The first command lists the mail servers, and the second lists text records such as SPF. Instead of the command line, you can use our DNS lookup tool. To see your domain's authentication records, our SPF, DKIM and DMARC checker helps.

Do not stop at one test. Send different kinds of messages from different providers: plain text, messages with links and messages with attachments. Attachments can hit size limits. These tries show how forwarding behaves in real use.

What should you check when forwarding does not work?

Instead of guessing, follow a path from symptom to cause. The table below summarizes the most common symptoms and the first place to look.

The bounce message often states the cause plainly. So read its first line before you change any setting.

What privacy and security risks does forwarding carry?

Forwarding to an outside address means the message passes through another provider's servers. If the message holds personal data, an invoice or a contract, you should do this on purpose. For company mail, the decision depends on the information security policy.

Attackers also try to add a silent forwarding rule to an account they took over. That way password reset messages flow to them as well. So keep your account password strong, turn on two-step verification and review forwarding rules now and then.

Forwarding a former employee's address forever can also create a personal data problem. This touches data protection law. This article is not legal advice; talk to your legal counsel or data controller before you act.

When should you not do it yourself and leave it to your hosting provider?

Adding a forwarder is a form in cPanel, and most site owners can do it comfortably. However, some situations belong to the provider.

• SRS or ARC support that has to be switched on at the server level is the provider's job.
• When the server's IP address lands on a blocklist, the fix sits with the provider.
• Forwarding thousands of messages while deliverability drops calls for expert help.
• Changing Google Workspace or Microsoft 365 admin policies belongs to your IT contact.

Also, running a mail server on your own VPS is a separate specialty. Protecting deliverability needs constant care. For most businesses, a ready-made mail service carries less risk.

If you want to think about your domain, DNS and email together with your hosting choice, see our guide to choosing web hosting.

Which forwarding method should you choose?

In short, choose by where the message needs to go. For a temporary, low-volume move, cPanel or Gmail forwarding is enough. For permanent, high-volume mail, an alias, a shared mailbox or a real mailbox is safer.

In every case, remember three things. Test first, then read the headers, and finally keep your forwarding map in writing. Also check your domain's DNS records and your backups regularly; our website backup strategy guide shows how.

If you want help with business email, site setup and infrastructure decisions, look at our web design service. We plan domain, DNS and mail decisions together with the overall setup of your site. Still, we suggest you configure the server-side mail settings with your hosting provider.

Which official sources back this guide?

We based the step-by-step information in this guide on the official sources below. Interfaces change over time, so check the current page before you act.

• cPanel documentation: Forwarders
• Gmail Help: automatically forward Gmail messages
• Microsoft Support: use rules to automatically forward messages
• RFC 7208: Sender Policy Framework (SPF)
• RFC 7489: DMARC
• RFC 8617: Authenticated Received Chain (ARC)