Forwarding alone protects your inbox on the way in. Reply-from-alias protects it on the way back out.
Why Normal Replies Expose You
If you reply to a forwarded message from your normal inbox, your mail client will usually send that reply from your real email account.
That means the recipient sees your real address unless there is another layer in between.
How MyShield Handles It
On Pro and Business, MyShield automatically generates a stable Reply Route (Reverse Alias) for your conversation, which looks like:
When you hit Reply, your client sends the message to this stable route. MyShield then identifies the alias and original sender, and relays the reply outward from the alias address.
What the Recipient Sees
The recipient sees the alias as the sender, not your real inbox address.
That keeps the conversation anchored to the alias instead of breaking compartmentalisation the moment you answer.
Stable Routes
To make reply-from-alias work, MyShield stores the mapping for these stable routes in its database. Unlike legacy single-use tokens, these routes are permanent for each specific conversation, ensuring you can continue long-running threads without worrying about expiration.
If you ever want to stop a specific sender from reaching you through a route, you can revoke it directly from your account dashboard.
Current Limits
The current reply relay is best thought of as a text-and-HTML reply path.
If your workflow depends heavily on outbound attachments or advanced client-side signing, test carefully before relying on it for that use case.
Plan Availability
Reply-from-alias is available on Pro and Business.
Ready to protect your inbox?
Start free - no credit card required
Three private aliases, instant forwarding, works with any inbox.
Create your free account