Owning a domain is easy. Receiving email on it reliably is harder. Running your own mail server means patching software, fighting spam, and worrying about whether a message from a client quietly bounced at 2 a.m. For most people with a personal site, side project, or small business, that is far more work than the problem deserves.
You can receive mail on any address at your domain, including ones you never set up, without maintaining a server. Here is how it works and what to watch out for.
What actually decides where your email goes
When someone sends a message to anything@yourdomain.com, their mail server looks up your domain’s MX records in DNS. These records name the servers that accept mail for your domain. Each record has a priority number, and lower numbers are tried first.
So you don’t need to run a mail server. You only need to point your MX records at a service that accepts mail on your behalf and then does something useful with it, such as forwarding it, storing it, or passing it to another app.
The catch-all address, explained
A catch-all (sometimes called a wildcard address) accepts mail sent to any address at your domain, even if it doesn’t exist. Mail to sales@, jon.smith@, or a typo like suport@ all lands somewhere instead of bouncing.
This is useful for a few common situations:
- Unique addresses per signup. Use shopname@yourdomain.com for each online store or newsletter. If one starts sending spam, you know who leaked or sold your address, and you can block just that one.
- Typos and old addresses. People misspell names. Former team addresses keep getting mail for years.
- Quick role addresses. You can hand out invoices@ or press@ on the spot without creating a mailbox first.
Step-by-step: setting it up without a server
- Choose an inbound email service. Many domain registrars and DNS providers include basic forwarding, and dedicated services handle inbound email routing for your domain with more control over rules and destinations. Pick one based on what you want to happen to incoming mail.
- Lower your DNS TTL a day ahead. If your current MX records have a long TTL, reduce it before switching. Changes then spread faster, and you can roll back quickly if something goes wrong.
- Replace your MX records. Remove the old MX entries and add the ones your provider gives you. Leaving old records in place can split your mail between two systems, which is confusing to debug.
- Turn on the catch-all and set a destination. Usually that’s your existing personal inbox, but it could also be a chat channel, a cloud storage folder, or a webhook for a script.
- Test from an outside account. Send mail to a real address, a made-up address, and one with an attachment. Check that all three arrive, including on your phone if that’s where you’ll read them.
The trade-offs nobody mentions up front
Spam goes up
Spammers often guess common names at a domain. With a catch-all, those guesses get accepted instead of rejected. Good inbound services filter spam before forwarding, but expect some extra noise. If it gets bad, switch from “accept everything” to a list of allowed patterns, or block the specific addresses that attract junk.
Forwarding can hurt deliverability
When a message is forwarded, the server relaying it isn’t the original sender’s server. That can cause SPF checks to fail at your final inbox. Reputable forwarding services work around this, often by rewriting the envelope sender (a technique called SRS) and leaving the original DKIM signature intact. Before you commit to a provider, ask how it handles this, or just test with mail from a few big providers.
Receiving isn’t sending
Pointing your MX records somewhere only covers incoming mail. If you want to reply from you@yourdomain.com, you need a sending setup too. That might be your email client’s “send as” feature with an SMTP service, plus SPF and DKIM records that authorize it. Otherwise replies will come from your personal address, or worse, land in spam.
Going beyond forwarding
Once mail flows through a routing service instead of a single mailbox, you can treat each address as a trigger:
- Send alerts@ to a team chat so server or monitoring notices aren’t buried.
- Save attachments from receipts@ straight to cloud storage for tax season.
- Pass orders@ to a webhook that updates a spreadsheet or app.
None of this needs a mailbox you have to clean out, and none of it needs a server you have to maintain.
A quick checklist
- MX records point only to your inbound provider
- Catch-all enabled, with a clear default destination
- Spam filtering on, with a way to block individual addresses
- Forwarding tested against your real inbox
- Separate sending setup if you need to reply from your domain
Set it up once, test it properly, and every email sent to your domain will end up somewhere you’ll actually see it.
