Email forwarding vs. a real alias inbox
Most email alias services forward mail to your existing inbox. mailservr takes a different approach with a built-in inbox. Here is why it matters.
How forwarding works
How a built-in inbox works
Side-by-side comparison
| Feature | Forwarding | Built-in Inbox |
|---|---|---|
| Your real address exposed | To your email provider | Never transmitted |
| Third-party dependency | Requires Gmail, Outlook, etc. | Self-contained |
| Threaded conversations | Depends on provider | Built-in |
| Search and filters | Depends on provider | Built-in per-alias filters |
| Reply from alias | Reverse-forwarding (complex) | Direct reply |
| Sender blocking per alias | Rarely supported | Built-in |
| API and webhooks | Varies | Full REST API + webhooks |
| Single point of failure | If provider blocks forwarding, all mail stops | No external dependency |
Your real address exposed
Forwarding
To your email provider
Built-in Inbox
Never transmitted
Third-party dependency
Forwarding
Requires Gmail, Outlook, etc.
Built-in Inbox
Self-contained
Threaded conversations
Forwarding
Depends on provider
Built-in Inbox
Built-in
Search and filters
Forwarding
Depends on provider
Built-in Inbox
Built-in per-alias filters
Reply from alias
Forwarding
Reverse-forwarding (complex)
Built-in Inbox
Direct reply
Sender blocking per alias
Forwarding
Rarely supported
Built-in Inbox
Built-in
API and webhooks
Forwarding
Varies
Built-in Inbox
Full REST API + webhooks
Single point of failure
Forwarding
If provider blocks forwarding, all mail stops
Built-in Inbox
No external dependency
When forwarding makes sense
- You already have a provider you love and just want address masking
- You want all mail in a single inbox alongside personal email
- You do not need API access or webhook integrations
When a built-in inbox wins
- You want full control with no third-party dependency
- You need per-alias sender blocking and triage tools
- You want API access and webhook-driven automation
- You prefer a purpose-built experience for alias email
Frequently asked questions
Is email forwarding safe?
Forwarding adds a middleman between your alias and your real inbox. If the forwarding service misconfigures headers or your email provider flags forwarded messages as spam, you can lose mail. A built-in inbox removes this risk entirely.
What is an alias inbox?
An alias inbox is a dedicated mailbox where emails sent to your aliases are stored and read directly, without forwarding to another provider. mailservr includes a threaded inbox with search, filters, and send/reply capabilities.
Can I switch from a forwarding service to mailservr?
Yes. Create new aliases on mailservr and update your accounts to use the new addresses. Your old forwarding service can continue receiving mail during the transition.
Try the built-in inbox approach
No forwarding. No third-party dependency. Just aliases with a real inbox.