Email Forwarding Services: How They Work and Why You Need One

Email forwarding is one of the oldest and most practical features of email infrastructure. You receive mail at one address and it automatically appears at another. Despite being simple in concept, forwarding solves a range of real problems — from consolidating multiple inboxes to running email on a custom domain without a full mail server.

How Email Forwarding Works

The mechanics are straightforward. When someone sends an email to your forwarding address, the forwarding server receives the message and re-sends it to your destination address. The original sender has no idea the forward happened — they only see the address they sent to.

Forwarding can work at several levels:

Address-level forwarding: A single address forwards to another single address. alias@example.com forwards everything to you@gmail.com.

Domain-level forwarding (catch-all): Every address at a domain forwards to a designated inbox. anything@yourdomain.com all routes to the same place.

Conditional forwarding: Rules determine which messages get forwarded and where. Messages matching certain criteria go to one inbox; everything else goes to another.

Why You'd Use Email Forwarding

Consolidating Inboxes

If you have email at multiple addresses — personal, work, side project, custom domain — forwarding lets you read everything in a single inbox. Instead of checking five different accounts, set up forwarding and manage everything from one place.

Running a Custom Domain

Email forwarding is the simplest way to receive mail at your own domain. Instead of running a mail server or paying for a hosted email service, you point your domain's MX records at a forwarding service and route incoming mail to your existing inbox.

Reusable.Email's custom domain support works this way. For $10 per year, you configure DNS records and receive email at any address on your domain. Messages can be read directly in Reusable.Email's interface, or forwarded from a managed inbox to another address.

Managing Aliases

Email aliases and forwarding are closely related. A forwarding alias is just an address that redirects mail to your real inbox. This is how services like SimpleLogin and AnonAddy work — they create alias addresses and forward incoming mail to your primary email.

For a detailed look at how aliases work with and without forwarding, see our email alias guide.

Transitioning Between Providers

Switching email providers is easier with forwarding. Set up forwarding from your old address to your new one, update your accounts over time, and eventually disable the forward. No messages are lost during the transition.

Types of Forwarding Services

Simple Forwarders

Services like ImprovMX and ForwardEmail.net do one thing: receive mail at your domain and forward it. They don't store emails, don't provide an inbox interface, and don't support sending.

Pros: Simple, often free for basic use, lightweight. Cons: No inbox to check, no send capability, if the forward fails the email is lost.

Full Inbox Services With Forwarding

Services like Reusable.Email provide a complete inbox that also supports forwarding. Mail arrives and is stored in the inbox — and can optionally be forwarded to another address.

Pros: Emails are stored even if the forward fails, full inbox features available, send capability. Cons: More setup than a simple forwarder, may cost more.

This is the more robust approach. If your forwarding destination rejects a message or is temporarily unavailable, the email still exists in the source inbox. Nothing is lost.

Reusable.Email's Approach

Reusable.Email handles forwarding through managed inboxes. When you have a managed inbox (one-time $3 payment), you can configure forwarding rules to send incoming email to any external address.

For custom domains, the catch-all feature receives email at any address on your domain. Each address can be linked to a managed inbox with its own forwarding rules. This gives you per-address control over where emails end up.

The key difference from simple forwarding services is that Reusable.Email stores the email regardless of forwarding. Your messages exist in the Reusable.Email inbox and can also appear in your external inbox. This means:

• No lost emails if the forward fails
• You can access messages through IMAP (imap.reusable.email:993) or the web interface even if you primarily read them in your forwarded inbox
• You can reply directly from the Reusable.Email address using SMTP (smtp.reusable.email:587)

For details on custom domain setup including DNS configuration, see Running Email on Your Own Domain. For the broader context of custom domain email, see our custom domain email guide.

When Forwarding Is Enough vs When You Need a Full Inbox

Forwarding is enough when:

• You just need to receive mail at a custom domain and read it in your existing inbox
• You're consolidating addresses and don't need to reply from the forwarded address
• You want a lightweight setup with minimal management

You need a full inbox when:

• You need to send or reply from the address (requires SMTP)
• You want to organize emails into folders
• You need spam filtering on the incoming address
• You want emails stored independently from your primary provider
• You need email client access (IMAP/POP3)

For most users, the practical answer is: start with forwarding and upgrade to a full inbox when forwarding's limitations become inconvenient. Reusable.Email makes this transition seamless — the address stays the same; only the capabilities change.

Email forwarding is a building block. By itself, it solves the routing problem. Combined with a real inbox, it becomes part of a flexible email infrastructure that adapts to how you actually use email.