Unsure whether to keep catch-all or set explicit aliases
Catch-all (anything that does not exist routed to one inbox) looks convenient but is a spam magnet and hides typos in real addresses. Explicit aliases are more work but much quieter and safer. For SMB, aliases nearly always win.
Try this first
- 1Inventory aliases you actually use: info@, sales@, hr@, support@, billing@, gdpr@. Keep it under 10.
- 2Disable catch-all in M365/Workspace, and configure only those aliases as shared mailboxes or aliases on a single user.
- 3For SaaS signups: use plus-addressing (you+slack@vectel.nl) instead of a disposable alias per tool.
- 4Document which alias maps to which person/group, schedule a yearly review.
- 5For inbound phishing: set DMARC to p=reject so spoofing your aliases does not even arrive.
When to bring us in
If you have a 15-year-old catch-all flooded with spam and want to replace it without losing real mail, we can plan a phased decommission.
See also
- Domain expires tomorrow and nobody saw the emailAn expired domain doesn't transfer instantly. There's a redemption window, but you pay extra.
- Unsure whether to enable auto-renewDisabling auto-renew only makes sense for domains you'll truly drop. For anything live, just keep it on.
- New registrar asks for auth code, can't find itEPP code or transfer code is the password to move a domain from registrar A to B.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.