Your reply shows your own address instead of the alias for one of three reasons: Can Reply is switched off on the destination you replied from, your account's permission mode blocks that destination, or you composed a new email instead of replying to the forwarded one. Fix the item that matches below and the alias shows as the sender.
You need an AliasFleet account with at least one verified destination. Replies only work on messages that arrived through an alias; they do not work on fresh compositions. To start a brand-new thread from an alias, use Quick Send, which uses Can Send instead.
How do I find which of the three checks is wrong?#
Go through the checks in order. Each one has a giveaway symptom, so most people land on their cause before they reach the end of the list.
- Confirm Can Reply is on for this destination. In the dashboard, open Destinations and find the one you are replying from. If its Can Reply toggle is off, the reply sends from your real address as normal, and that is what the other person sees. Flip the toggle on. If the toggle is greyed out and will not flip, that destination is not verified yet, so finish verification first. The setup walkthrough is in Reply from Aliases.
- Check your account's permission mode (Strict vs Open). Permission mode is a single account-wide setting, not something you set per alias. Go to Settings, open the Aliases tab, and find the Alias Permission Mode card. Under Strict, only the destination linked to an alias may reply through it, so a reply from anywhere else gets blocked. Under Open, any verified destination with Can Reply switched on may reply through any alias. Only switch to Open if you really do use one alias from more than one destination; Strict is the right default for most people. Full details are in Alias Permission Mode: Strict vs Open.
- Reply to the forwarded email, not a new compose. AliasFleet routes your reply by reading the alias routing stored in the forwarded message's headers. Start a fresh email and those headers are not there, so the reply has nothing to attach the alias to. Always hit reply on the forwarded message itself.
What does a blocked reply look like?#
A blocked reply never disappears quietly. AliasFleet sends you a bounce email that names the exact cause, such as a disabled Can Reply toggle or a destination shut out by Strict mode. That bounce email also carries a one-click link that switches on the right setting, so you can often sort it straight from your inbox without opening settings at all.
Troubleshooting table#
| Symptom | Most likely cause | Fix |
|---|---|---|
| Reply went through, but it shows your real address | Can Reply is off on the destination you replied from | Flip Can Reply on for that destination under Destinations |
| Reply bounced with a permission message | Strict mode blocked the destination, or Can Reply is off | Reply from the linked destination, or switch the account to Open mode |
| Can Reply toggle is greyed out | Destination not verified | Complete destination verification first |
| Reply seems to send but never goes out as the alias | You composed a new email instead of replying | Reply to the forwarded message; use Quick Send for new threads |
| The forwarded mail itself never arrives | This is a forwarding problem, not a reply problem | Fix delivery first, then come back to replies |
How do I verify the fix?#
Send a real test reply after each change. Answer a forwarded message from the destination you just fixed and confirm the reply arrives showing the alias as the sender. If you switched the permission mode from Strict to Open, reply again from the second destination and check that one now goes through. Still bouncing? Open the newest bounce email: the cause it names may have changed, which tells you a different check now needs attention.
Why do my replies work from one alias but not another?#
Because permission mode and Can Reply combine per destination, not per alias. Can Reply can be on for one of your destinations and off for another, and under Strict mode a destination is only valid for the aliases linked to it. Put the two aliases side by side: note which destination each is linked to and whether Can Reply is on for the one you are replying from. The gap between the two setups usually gives you the answer. For how the reply routing works under the hood, see how email aliases actually work.
Still not working?#
Contact support with the alias address, the destination you replied from, and roughly when you tried. If AliasFleet sent you a bounce email, paste its message into your note: it already names what was blocked, which saves a round trip.