One-click enable is a link in a bounce notification email that switches on the permission which blocked an action. When Can Reply or Can Send is off for a destination, an attempted reply or send from an alias is stopped, and a bounce notification goes to the destination inbox. Following the link switches on only that permission, for that destination.
This page describes the events that produce the bounce email, the contents of that email, the steps for enabling the permission from the email, the checks that confirm the result, and the fixes for a link that does not work.
Access to the destination inbox is required, because the bounce notification email arrives there. The destination must already exist in the account. No separate verification step is needed to use the link itself, since the link is tied to the account owner.
Bounce triggers#
A bounce notification is produced when an action requires a destination permission that is currently off. Two cases produce it:
- Reply blocked: a reply to a forwarded message is attempted while Can Reply is off on the destination used for the reply.
- Send blocked: a message is sent from an alias while Can Send is off on the destination used for the send.
In both cases the attempted message is not sent. AliasFleet sends a bounce notification email to the destination inbox instead, so the block is visible in the same inbox where the reply or send was attempted.
One example illustrates the sequence. Can Reply is off on a personal inbox destination, and a reply to a forwarded newsletter message is attempted from an alias. The reply is blocked, and a bounce notification email arrives in the personal inbox. The email names the blocked action and the permission involved, and it carries the one-click link for switching Can Reply on for that destination.
Bounce email contents#
The bounce email is short. It states that the action was blocked because Can Reply or Can Send is disabled on the destination, and it provides a link or button near the bottom for enabling that permission. The wording for the link is hedged in this guide on purpose: the button is labelled something like "Enable Reply for this destination" or "Enable Send", and the exact label is not stated here because it was not verified against the live interface for this rewrite.
The email changes no other setting. It does not enable the permission on any other destination, and it does not switch the permission on for both reply and send at once. Only the one permission named in the bounce changes.
Enabling the permission#
- Open the bounce notification email in the destination inbox that received it.
- Find the enable link near the bottom of the email, labelled something like "Enable Reply for this destination" or "Enable Send".
- Click the link. The permission is toggled on for that destination immediately.
- Check the confirmation page. The page reached from the link confirms that the permission is now enabled.
- Retry the blocked action. Send the reply or the message from the alias again, in the usual way.
No login step and no navigation through settings is needed for this path. The link itself carries the account and destination context, which is why it works from the email alone.
Verification#
After the link is clicked, the confirmation page is the first check: it states that the permission is enabled. A second check is available in the dashboard. Open Destinations, locate the destination named in the bounce, and confirm that the matching toggle, Can Reply or Can Send, is on.
The strongest check is the next attempt itself. When the same reply or send is retried and goes through normally, the permission is in the state the action needs. If the retry is blocked again by a second bounce email, the permission named in that second email is a different one, and the same one-click steps apply to it.
Link failures#
A link that does not work has a small set of likely causes, and each has a direct fix:
- Link already used. The link is single-use. Clicking it a second time does nothing further, because the permission is already enabled from the first click. Check the toggle in Destinations to confirm.
- Link expired. An expired link no longer enables the permission. Open Destinations and toggle Can Reply or Can Send on manually. The manual toggle produces the same result as the link.
- Opened from a different account. The link is tied to the account owner, so it does not enable a permission on another account. Sign in to the account that owns the destination, then use the manual toggle in Destinations.
- Wrong inbox. The bounce email arrives in the destination inbox, not in a separate mailbox. If the email cannot be found, check the destination inbox for the bounce before searching elsewhere.
The manual path is always available as the fallback: open Destinations, locate the destination, and toggle Can Reply or Can Send on. For background on the reply flow itself, see Reply from Aliases. For the case where a destination is not yet confirmed at all, see Verifying a Destination.
Repeat bounce emails#
Repeat bounce emails mean the permission is still off at the time of each attempt. The durable fix is to leave the permission on. Open Destinations and toggle Can Reply or Can Send on permanently for the destinations used for replies and sends, so the feature is available whenever it is needed.
If bounces continue after the toggle is confirmed on, check that the attempts are using the same destination the toggle was set on. An account with more than one destination can have Can Reply on for one destination and off for another, and a bounce names only the destination that blocked that attempt.
For background on how an alias forwards to a destination inbox, see How Email Aliases Actually Work.