Adding a destination registers a real inbox address that receives mail forwarded from AliasFleet aliases. This page covers the complete add flow and the verification step the reader must complete before aliases can forward to the new inbox: opening the Destinations page, entering the address, requesting a verification code, and confirming the address.
Access to the inbox is required, because the verification code is sent to the address being added. The address must be an inbox owned by the account holder and able to receive mail, and it must not already be in use on the same account. The number of destinations allowed depends on the plan, and current usage is shown on the Billing page.
Destination definition#
A destination forms the final point in the forwarding chain: mail addressed to an alias ends in this real inbox. The alias functions as the public address shared with senders, while the destination remains the private inbox behind it. Because one account can hold several destinations, separate aliases can point at a work inbox and a personal inbox respectively. Senders never see the destination address; only the alias is visible to them. How Email Aliases Actually Work explains the chain in full.
Adding a destination#
- Open the Destinations page. Select Destinations in the dashboard, or open /destinations/new directly.
- Begin the add flow. Select Add Destination, or the + button on mobile.
- Enter the inbox address. Type the complete address of the inbox that will receive forwarded mail. Ownership by the account holder and the ability to receive mail are both required.
- Request the verification code. Choosing Send Verification Email sends a 6-digit code to that inbox, provided the address is valid and not already in use on the account.
- Complete verification. Verification finishes either by entering the 6-digit code on the verification screen or by opening the verification link in the verification email. The link option requires no code entry. Full detail on both options is in Verifying a Destination.
Verification outcome#
Completion of verification marks the destination as ready for use. Once ready, it can be assigned to aliases without delay, and mail to those aliases forwards to it. Until verification completes, forwarding to that destination is not possible, so the verification step must be completed first.
Missing verification email#
Brief delays occur, so a minute should pass before further action. The spam folder is the next place to check, since verification mail sometimes arrives there. When the email remains missing, the Resend email option on the verification screen requests another copy. Resends are limited by a 30-second cooldown, and 3 failed code attempts trigger a 15-minute block as a security measure. Persistent blocks or other failures are covered in Can't Verify a Destination.
Destination limits#
The plan determines how many destinations an account may hold, with current usage displayed on the Billing page. Removal of a destination is possible, but aliases assigned to it cease forwarding unless reassigned beforehand, as the removing-a-destination guide describes. Choice of a default destination for new aliases is a separate setting, covered in Setting a Default Destination.
Related guides#
- Verifying a Destination: the code and link verification options in full.
- Setting a Default Destination: which destination new aliases use.
- Can't Verify a Destination: fixes for failed verification.
- How Email Aliases Actually Work: how an alias forwards to a destination inbox.