A per-address email forward routes mail for one address at a managed domain to another mailbox. It does not create a new destination inbox and does not redirect the domain’s website.

Confirm mail routing first

Open PD Modules → Forwarding → Domains, identify the domain and provider, then choose Actions → Forwarding. Confirm that the provider supports email forwarding and that the domain’s intended incoming-mail route is ready.

Do not switch the domain’s mail routing away from an existing mail service merely to add one address. In particular, enabling Cloudflare Email Routing changes how incoming mail for the domain is handled; a saved forward cannot replace that preparation. Ask the administrator responsible for the domain’s mail to review any required change.

Create the address forward

1. Choose Add email forward in the domain’s forwarding panel.
2. In Forward this mailbox, enter the full source email address, including the domain. This administrator form expects the full address, rather than only its mailbox name.
3. Enter the destination in Forward to. Use one destination mailbox whose owner expects the forwarded mail. A form accepting a comma-separated list does not prove the provider supports multiple destinations for this rule.
4. Choose Create forward and read the result. A confirmation-related response is different from a rule that is already delivering mail.
5. Reopen the domain’s forwarding panel and review the intended source and destination. If the list could not be read, resolve that error rather than assuming the rule is absent.

Complete destination confirmation

Cloudflare requires destination verification. The intended recipient must use the confirmation message sent by the provider; it cannot be confirmed on their behalf inside the module. Registration or permission failures can also prevent the message from being sent, so an absent message is not proof that it was delivered to the recipient.

A pending single-address forward has not yet become a working provider rule. The module can retry pending creation when the customer opens that domain’s forwarding page after confirmation. Do not assume any administrator-page refresh or background run will complete it. If it remains pending, check the destination confirmation and current provider rule before adding the same forward again.

Check delivery and later changes

Use an authorised, non-sensitive test message through your normal mail testing process. Confirm receipt in the destination mailbox, including its filtering or rejection result where relevant. An active row alone does not prove end-to-end delivery.

Changing an existing email forward is a replacement operation. If the new destination needs confirmation, the old route may already have been removed while the new one is pending. A failed-change message is not sufficient proof that the previous rule was restored. For a working mailbox, plan the change with the mail administrator and verify the actual route afterwards.

Do not share the confirmation link, provider token, private mail content or full customer mailbox list in public screenshots.

See the PD Domain & Email Forwarder WHMCS guide for the wider workflow, or explore the module.