Use a Plesk catch-all when mail for unknown recipients on a domain should reach one intended mailbox. This changes the native domain’s unknown-recipient policy; it is different from creating a forward for one named address.

Prepare the intended mail policy

Confirm the domain exists, the mail service is enabled and the provider account may change its preferences. Check MX routing and verify the destination mailbox independently.

Keep the previous unknown-recipient policy for comparison. Catch-all handling receives messages for unmatched names, including mistyped or unwanted addresses; decide whether that matches the intended mail service.

Set and verify

1. Open the intended domain’s Forwarding page and its catch-all controls.
2. Enter the single intended receiving mailbox.
3. Save and read back the current catch-all destination.
4. Send a controlled message to an unused address on the domain.
5. Confirm the destination receives it, then test a normal mailbox separately.

Existing named mailboxes and single-address forwards keep their own matching behaviour. A catch-all cannot correct MX routing that sends mail elsewhere or create the destination mailbox.

Remove deliberately

Removing the module catch-all sets Plesk’s unknown-recipient handling to reject. It does not automatically recover an arbitrary earlier policy. Review the desired replacement with the mail administrator before removing it.

Use the removal guide and inspect actual native settings after a failed or uncertain request. Retain the original action time and redacted delivery result while your hosting team checks the actual mail route, without keys or full mail contents.

Check unknown-recipient handling

Your hosting team should compare the native domain’s unknown-recipient policy and current catch-all destination with the intended mail service. Check mail-service permission, MX and destination delivery separately from the module’s saved result. An unmatched recipient and a real mailbox or alias exercise different routes. Removal sets unknown-recipient handling to reject; agree any replacement with your Plesk mail administrator rather than expecting a previous policy to return.

See the PD Plesk DNS Blesta guide for related tasks, or explore the module.