Email Forwarding Service: What It Does and Where It Breaks

An email forwarding service takes mail sent to your domain and redirects it to an inbox you already have. Gmail, Outlook, wherever. That's the whole job. Tools like ImprovMX, Cloudflare Email Routing, Addy.io, SimpleLogin, and Forward Email all do it well, and several do it for free. The catch is that forwarding isn't an inbox: you can't reply from the address without extra SMTP setup, and the moment you run more than one domain you're stitching together three or four tools. Here's what forwarding actually does, where it breaks, and how to tell when you've outgrown it.

What an email forwarding service actually does (and where it stops)

Strip away the marketing and email forwarding is a one-way pipe. Mail hits you@yourdomain.com, a rule catches it, and it lands in your existing Gmail or Outlook inbox. No new mailbox gets created. Most providers don't store your mail long-term. It's plumbing, not a mail client.

That's exactly why it's cheap or free. You're not paying for storage or an interface. You're paying (or not paying) for MX record routing.

Here's how the well-known email forwarding software options handle it:

• Cloudflare Email Routing: free, unlimited inbound volume, up to 200 routing rules per domain and 200 verified destinations per account. No inbox. Cloudflare does sell outbound sending now, but as a separate paid, API-only product; we broke that down in our guide to sending with Cloudflare Email Routing.
• ImprovMX: free plan covers 1 domain with 25 aliases, receive-only. Premium at $9/month gets you 30 domains and SMTP sending (6,000 sends/month); the $24/month Pro tier stretches to 100 domains.
• Addy.io (formerly AnonAddy): free tier gives unlimited standard aliases but caps bandwidth at 10MB/month. Pro is $3-4/month for custom domains. Built for alias privacy, not business inboxes.
• SimpleLogin: free plan allows 10 aliases with no custom domain. Premium is $30/year for unlimited aliases and domains. Still alias-first, same privacy job as Addy.
• Forward Email: open-source, free hosted forwarding for unlimited domains. Add IMAP/SMTP send and receive and it's $3/month. Self-hosting is possible, but now you're running a mail server.

All five are legit domain email forwarding tools. r/selfhosted and r/webdev recommend this exact stack constantly for cheap custom-domain email. For one domain, one person, one inbox to check, it works.

Where forwarding falls apart

• Replying looks wrong. Hit reply on a forwarded message and it goes out from your personal Gmail, not the domain the mail came to. Gmail's "Send mail as" workaround increasingly fails DMARC, so replies land in spam or show "via gmail.com". We covered the mechanics in how to reply with Cloudflare Email Routing; the same physics apply to every forwarder.
• Every extra domain multiplies the mess. Run hello@brand-a.com and support@brand-b.com through forwarding and you're juggling identity per reply inside one Gmail, or logging in and out of separate accounts. The full pain is its own post: one inbox for multiple domains.
• No shared access. Forwarding rules point at one personal inbox. Add a cofounder or a support person and you're sharing a password or buying seats somewhere else.
• No real archive. Most forwarders relay and forget. If the destination inbox dies or you switch providers, there's no independent copy of your mail history.

Forwarding solves "get the mail somewhere". It was never built to solve "run a business's email across domains".

When you've outgrown forwarding

We built Mailyond for the point where the free stack stops being free in time terms: the founder with 3, 5, 10 domains who's already duct-taped Cloudflare rules to Gmail Send-As, lost a weekend to SPF and DKIM, and still can't reply cleanly as the right brand. (That founder was us. Mailyond runs on the fifth iteration of the setup that broke four times.)

What changes with an actual multi-domain inbox:

• One inbox, every domain. All your domains' mail in a single threaded view, tagged per domain, stored independently of any upstream provider.
• Reply as the right address, correctly. Each domain is verified with one 5-minute DNS setup (DKIM, Return-Path, MX), so replies go out signed and pass DMARC. No "via gmail.com".
• Send from your app too. A transactional send API on the same domains, Resend-compatible, so receipts and password resets don't need a second vendor.
• A different job than aliasing. Addy.io and SimpleLogin are excellent at hiding your real address for privacy. Running a company's support and sales email across brands is a different job, and that's the one Mailyond does.

The honest version: if you just need mail redirected, use a forwarder. Cloudflare's is free and good. Mailyond is for when you also need to reply, send, and keep the history, across more domains than you have teammates.

Pricing logic: per domain, per seat, or per bundle

This is where most comparisons get lazy, so let's be specific.

Forwarding tools price per domain or per volume: ImprovMX at $9/month for 30 domains, Addy.io Pro at $3-4/month, Forward Email at $3/month, Cloudflare at $0. Cheap. But none of those prices include the actual mailbox: you still need somewhere to read and reply, which usually means Google Workspace at $7-14 per user per month on top (full breakdown here). A 3-domain setup with a "proper" inbox per brand quietly becomes $30-50/month.

Workspace prices per seat, which is the wrong axis for a solo founder with five brands: you have more domains than people.

Mailyond prices per bundle of domains: $10/month covers 5 domains with 3,000 emails, inbox and send API included; $40/month covers 30 domains for agencies. Adding a project doesn't change the bill. The question to ask before picking a tool: are you paying for people, or for domains? If you've got more domains than teammates, per-seat pricing is the wrong deal.

FAQ

What's the difference between email forwarding and a hosted mailbox? Forwarding redirects incoming mail to an inbox you already have; no storage, usually no sending. A hosted mailbox stores mail, lets you reply as that address, and keeps a searchable history in one place.

Is free email forwarding actually free? Cloudflare Email Routing and Forward Email's basic tier are genuinely free with no time limit. The catch is they're receive-only or capped, and you still need an inbox to receive into.

Can I reply from a forwarded address without it looking spammy? Only if SPF, DKIM, and DMARC authorize the sending inbox for that domain. Skip that and replies land in spam or show "via gmail.com". This got strictly worse after the 2024 DMARC tightening.

What is MX forwarding? Changing your domain's MX records to point at a forwarding provider's servers, which relay mail to your real inbox. It's the mechanism behind every tool in this article.

Do I need email forwarding software if I only own one domain? Probably just a free option like Cloudflare Email Routing. Multi-domain inbox tools earn their price once you're managing several domains or need shared access.

The short version

An email forwarding service is a redirect rule, and for one domain the free ones (Cloudflare, Forward Email) are genuinely enough. The breakage starts when you reply, and it compounds with every domain you add: broken DMARC, juggled identities, no shared access, no archive. If that's where you are, forwarding isn't the tool anymore. One 5-minute DNS setup per domain gets you an inbox that receives, replies, and sends as every domain you own.