A catch-all routes mail for otherwise unmatched addresses at a domain to a destination mailbox. Use it when that broad coverage is intentional, rather than as a substitute for a specific address forward.

Review the mail arrangement

Open PD Modules → Forwarding → Domains, confirm the domain and provider, then choose Actions → Forwarding. Check the existing address forwards and the domain’s incoming-mail service with the administrator responsible for mail.

Provider capabilities and mail-server configuration determine whether catch-all forwarding is available. Do not assume every backend supports the same delivery or matching behaviour. A specific-address forward and a catch-all can interact differently across providers, so verify the intended matching result.

For Cloudflare, prepare a verified destination and the intended Email Routing configuration first. The module’s catch-all path does not follow the same automatic destination-registration and pending-rule process as a new single-address forward. Do not promise that setting a catch-all will automatically send a destination-confirmation message.

Set or change the catch-all

1. Choose Set catch-all in the domain’s forwarding panel. If one is already shown, review its current destination and use Change destination for the existing catch-all.
2. Enter the intended destination in Send all unmatched mail to. Use one intended destination. Do not assume a comma-separated list is supported merely because the form accepts it.
3. Review the scope before choosing Set catch-all or Save catch-all, as shown. This changes the domain-level catch-all, rather than adding another independent one.
4. Read the outcome and reopen the panel. Check that the intended catch-all is visible and that the provider list was read successfully.

If the catch-all could not be read, No catch-all set can be inconclusive. Ask the authorised administrator to inspect the provider state before replacing what might be an existing rule. A confirmation or permission error needs investigation; the catch-all is not automatically retained as a pending single-address rule.

Verify the scope and delivery

Use a controlled unmatched address to verify the expected route and confirm receipt with the destination owner. Check an explicit address forward separately if both kinds exist. A provider rule being enabled does not prove that the domain’s DNS and incoming-mail route are correct or that the destination accepted the message.

Only use Remove catch-all when removing that broad routing is intended. It is different from removing one specific-address rule or deleting the destination inbox. Check what happens to unmatched mail afterwards. If removal fails or its outcome is unclear, reconcile the actual provider rule before trying again; a missing local overview row is not proof of successful removal.

Keep destination details, mail contents and credentials out of public screenshots.

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