A catch-all address captures mail sent to any address at your domain, even ones you haven't explicitly defined — useful in some scenarios, though it comes with real spam and management trade-offs worth understanding.
What a Catch-All Does
Without a catch-all, mail to an undefined address (like a typo, or an address that never existed) bounces — with a catch-all configured, all such mail instead delivers to one designated mailbox rather than bouncing.
Legitimate Use Cases
- Testing which specific address a particular signup/service uses (creating unique addresses per service to trace potential data leaks)
- Catching typos from customers/clients sending to a close-but-slightly-wrong address
- A transition period after removing specific aliases, ensuring nothing bounces immediately
The Real Downside: Spam Volume
Since a catch-all accepts mail to literally any address at your domain, it also accepts every spam message using random/guessed addresses at your domain — this can result in substantially more spam volume than a domain without a catch-all.
Setting Up a Catch-All in Postfix
sudo nano /etc/postfix/virtual@yourdomain.com [email protected]sudo postmap /etc/postfix/virtual
sudo systemctl reload postfixAny mail to an undefined address at yourdomain.com now delivers to [email protected] instead of bouncing.
Important: Order Matters
Ensure specific aliases (see How to Set Up Email Aliases and Forwarding) are defined before the catch-all wildcard entry — specific matches should take precedence over the general catch-all rule.
Mitigating Spam Volume with a Catch-All
If using a catch-all, strong spam filtering becomes even more important — see How to Configure SpamAssassin for Spam Filtering; without it, a catch-all can become a significant spam magnet.
Alternative: A Reasonably Comprehensive Alias List Instead
Rather than a full catch-all, consider explicitly defining every address you actually expect to receive mail at, letting genuinely undefined addresses bounce — more effort to maintain, but avoids the spam volume increase entirely.
Monitoring Catch-All Volume
Periodically review what's actually arriving at your catch-all mailbox — both to catch genuinely important misdirected mail, and to assess whether spam volume has become unmanageable, in which case reconsidering the catch-all approach is reasonable.
Disabling a Catch-All
# Remove or comment out the wildcard line
# @yourdomain.com [email protected]sudo postmap /etc/postfix/virtual
sudo systemctl reload postfixCommon Errors
Legitimate mail buried in catch-all spam volume — a sign the catch-all approach isn't working well for your situation; either strengthen spam filtering significantly or move to explicit address-only delivery.
Continue Reading
- How to Set Up Email Aliases and Forwarding
- How to Configure SpamAssassin for Spam Filtering
- How to Install and Configure Postfix as a Mail Transfer Agent
Browse more articles in Email Hosting & Deliverability.
