This is intended as a helpful resource guide for iBuild.PH customers using our standard cPanel webmail hosting and potential clients inquiring about email forwarding.

Email forwarding has long been a convenient feature for website owners. With a simple setting in cPanel, you could forward messages from email@yourdomain.com to your personal Gmail, Yahoo, or Outlook address.

However, beginning in the last few years, especially after major changes in 2024, many users noticed that forwarded messages no longer arrive, are marked as spam, or disappear completely without warning.

If you are an iBuild.PH client is wondering why email forwarding does not work like it used to. This guide explains the causes and what you can do to ensure reliable email delivery.

Email forwarding not working anymore - the short answer

Email forwarding still exists, but it fails more frequently because Google, Yahoo, and Microsoft now enforce strict authentication rules such as DMARC, SPF, DKIM, and ARC. When a message is forwarded through a cPanel server, these security checks often break, causing providers to reject or drop the message.

Modern email security rejects most forwarded messages

DMARC enforcement (the number one reason)

Most major email providers now use DMARC policies like:

v=DMARC1; p=reject; 

This tells receiving servers:
If SPF or DKIM fails, reject the message.

When an email is forwarded by a cPanel server:

• SPF becomes invalid
• DKIM signatures may break
• DMARC rejects the message

Gmail or Outlook then blocks or discards the email.

SPF fails when emails are forwarded

SPF verifies that the sending server is approved by the domain owner.

Example:

You receive an email from sender@company.com, routed to your cPanel inbox.
When forwarded to Gmail:

• Gmail sees your cPanel server sending mail on behalf of company.com
• Your server is not listed in company.com’s SPF record
• Result: SPF fails, and the message is rejected or placed in spam

DKIM signatures often break on forwarded messages

DKIM ensures that the message content has not been altered. Forwarding can modify headers or add filtering information, which breaks the DKIM signature.

A broken DKIM signature combined with a failed SPF check triggers DMARC rejection.

Gmail and Yahoo implemented stricter rules in 2024

In 2024, Gmail and Yahoo both rolled out new anti-spam requirements. These include:

• mandatory sender authentication
• higher scrutiny for forwarded emails
• requirement for ARC or Authenticated Received Chain

Many cPanel servers do not support ARC by default, which increases the likelihood of forwarding failures.

Why this matters for iBuild.PH customers or cPanel webmail users

If you rely on cPanel email forwarding, you may notice:

• missing emails
• messages are going directly to spam
• delayed forwarding
• clients claiming they emailed you, but no message reaches your inbox

This is caused by global email authentication standards rather than an issue with your domain or hosting provider.

Recommended solutions (best practices for reliable email)

Option 1: Use Gmail’s check mail from other accounts (POP3)

This is the most reliable solution for Gmail users. Instead of forwarding, Gmail retrieves your emails directly from your cPanel mailbox through POP3.

Benefits:

• fully DMARC compliant
• no lost or rejected messages
• reliable syncing
• easy setup

iBuild.PH can assist with the technical configuration if needed, inclusive to webhosting support for subscribed hosting clients.

Option 2: enable ARC support if available

ARC helps Gmail verify that your server is simply forwarding the message. Some hosting providers support this, and some do not.

iBuild.PH can check availability for your hosting plan.

Option 3: redirect MX records to Gmail using Google Workspace

For businesses that rely on Gmail as the primary inbox, Google Workspace is the most dependable option.

Incoming email goes directly to Gmail instead of passing through cPanel.

This avoids all forwarding issues.

Option 4: Use rewriting as an advanced option

Some servers rewrite the sender address:

Original:
From: sender@company.com

Rewritten:
From: yourdomain.com with Reply-To pointing to sender@company.com

This avoids SPF-related problems but changes the visible sender.
This is recommended only for specific situations.

What iBuild.PH recommends

To ensure consistent email delivery, we generally recommend:

• POP3 retrieval for Gmail users
• Google Workspace or Microsoft 365 for businesses and teams
• ARC-enabled forwarding for technical users when available

These approaches avoid the deliverability issues associated with traditional cPanel forwarding.

Conclusion

Email forwarding is no longer dependable due to modern email authentication rules. SPF, DKIM, and DMARC often fail when messages are forwarded through cPanel, which causes missing or rejected messages.

iBuild.PH offers solutions such as:

• Gmail POP3 setup
• Workspace email routing
• ARC support when available
• Proper DNS and authentication configuration

If you need help improving your email reliability, the iBuild.PH team is ready to assist.