Yes, but disabling is almost always the better move — and on a catch-all domain, deleting can be actively counterproductive. Disabling keeps the address on record and refuses mail to it. Deleting removes the record entirely, which on a catch-all setup means the next message addressed to it simply recreates the alias and starts delivering again. Keep the alias, leave it off.
Delete vs disable
| Disable | Delete | |
|---|---|---|
| Mail to the address | Refused | Refused — unless catch-all recreates it |
| The record | Kept, marked off | Gone |
| Its history and statistics | Kept | Usually lost |
| Reversible | Yes, one action | Only by recreating it |
| On a catch-all domain | Stays off permanently | Recreated on next inbound mail |
| Blocked attempts logged | Yes, on services that log them | No |
The catch-all trap
A catch-all domain accepts mail for any address at it and creates the alias on first use. That's what makes per-service addresses effortless — you invent the address at the signup form.
It also means deletion isn't a permanent state. Delete spammyshop@yourdomain.com and the domain no longer knows about it — so the next message addressed there looks like a brand-new address, gets created, and is delivered. You've reset it to allowing mail.
To permanently stop a sender, disable the alias and leave it in place. The disabled record is what tells the server to refuse rather than create. How catch-all works
Why the history is worth keeping
A disabled alias is a record of a company that behaved badly. It tells you which organisation leaked or over-mailed you, when, and — on services that log blocked attempts — who kept trying afterwards.
That accumulates into something genuinely useful: a personal record of which companies treat data carefully. Deleting throws it away for no benefit.
When deleting is fine
- You made a typo creating an alias and nothing has used it.
- You're not on a catch-all setup, so deletion is genuinely terminal.
- You're leaving the service and clearing out, having already migrated the accounts that matter.
- Genuine clutter — a handful of test addresses. Even then, disabling costs nothing.
The thing neither does
Worth stating plainly: neither deleting nor disabling removes your address from anyone's database. The company still has it, and so does anyone they sold it to. You've closed the door, not erased the record — they can keep sending, it just bounces.
If deleting the underlying record is what you want, that's a different mechanism entirely. Removal vs prevention
The rule
Disable, don't delete. It's reversible, it keeps the evidence, it survives catch-all, and it costs nothing to leave in place forever.
And the safety rule that goes with it: never disable an alias attached to an account you still use, or its password resets bounce too. Avoiding lockouts