Forward Domain Email to Gmail and Separate Send Mail As

Receiving domain mail in Gmail and sending as a domain address are separate tasks. An incoming forwarder belongs on the system that receives your domain’s mail. Gmail’s Send mail as setting configures an outgoing identity; verifying that identity does not create incoming forwarding.

Forward incoming mail from cPanel

1. Confirm that the domain’s mail arrives at your cPanel hosting server. If MX records point to another provider, configure forwarding there instead.
2. Open the verified HTTPS cPanel interface, then Email > Forwarders > Add Forwarder.
3. Select the source local part and correct domain. Enter the Gmail address you control as the full destination and save.
4. Review the saved pair and send a harmless message from a separate external account. Check Gmail’s inbox and spam folder, the local mailbox if present, and the hosting delivery result.

A matching local mailbox generally retains its copy, so forwarding does not stop that mailbox from filling. Do not delete an account or its old messages just to troubleshoot. Follow the cPanel forwarding guide for changing/removing the exact rule and understanding local copies.

Optionally send as your domain address

In Gmail’s desktop settings, the Accounts and Import or Accounts section offers Send mail as > Add another email address where supported. Follow Google’s current flow, verify control of the address and supply the authorized SMTP service when requested. Use its required TLS mode, port and credentials; do not submit an unrelated hosting-control-panel password.

Receiving a verification message proves access for that verification step, not that all future forwarded mail will be accepted. The outgoing identity also needs correct domain authentication and service authorization. Review reply/default-address behavior so recipients see the intended address rather than assuming the incoming forwarding rule handles replies.

Understand forwarding limits

Forwarding can affect SPF evaluation, while DKIM can fail if message content is changed. Gmail can filter or reject mail based on authentication, reputation, size, quota and policy. Neither forwarding nor adding an address to contacts guarantees inbox placement. Avoid loops and do not bypass anti-abuse checks. For persistent failures, provide a support ticket with timestamps, a redacted delivery error and the source/destination pair, not passwords or private message bodies.

References: Gmail Send mail as, Google forwarding practices and cPanel forwarding behavior.

Reviewed October 15, 2026. No Gmail identity, SMTP credentials, DNS or customer forwarder was changed or tested.