Send New Emails from Aliases

Can Send is a destination permission that allows new emails to be sent from an alias address. With it enabled, the recipient sees the alias as the sender and does not see the real inbox address. This page covers enabling Can Send on a verified destination, the two methods for sending a new email, confirmation that a message went out, and fixes for common failures.

Enabling Can Send#

1. Open Destinations. In the dashboard, go to Destinations.
2. Find the destination. Select the destination the alias is assigned to, or the destination that will be used for sending.
3. Toggle Can Send on. Switch the Can Send toggle to on for that destination.
4. Check the permission mode. In Strict mode, only the destination the alias is assigned to can send through it. In Open mode, any destination with Can Send enabled can send. See Alias permission mode for the full rules.

Can Send and Can Reply operate independently. Each destination can have one, both, or neither enabled.

Sending a new email#

Two methods exist for sending a new email from an alias. The right method depends on where the message is written.

Method 1: Relay address from a mail app#

Use this method when the message is composed in a personal mail app instead of the AliasFleet dashboard.

1. Find the relay address. The relay address and its instructions are shown in the account, in the destination detail or in the alias detail. Open the destination or alias to be sent from and copy the relay address displayed there.
2. Write the message in the mail app. Compose a new email from the real inbox, addressed to the relay address.
3. Add the final recipient. Include the intended recipient in the message in the way the relay instructions specify, so AliasFleet knows the delivery target.
4. Send. AliasFleet receives the message and re-sends it to the final recipient with the alias as the from address. The recipient sees the alias, not the real inbox address.

Method 2: Quick Send composer in the dashboard#

Use this method when the message is composed in the AliasFleet dashboard, without opening a mail app. Quick Send is the built-in composer for new outbound emails from an alias.

1. Open the composer. In the dashboard, look for Compose or Quick Send and select it.
2. Choose the sender alias. In the From alias field, select the active alias the recipient should see.
3. Add recipients. Enter the recipient address in the To field. Add Cc or Bcc addresses where needed.
4. Write the message. Add a Subject, then write the body.
5. Send. Press Send. AliasFleet sends the email from its servers, using the alias as the sender.

Quick Send supports attachments on Pro and Business plans, up to a combined total of 18 MB per email. For the full composer guide, including the blocked file types, see Sending Outbound Emails (Quick Send).

Which method fits which use#

The relay address method fits when the draft, signature, or sending habits already exist in a personal mail app. Quick Send fits when the message starts in the dashboard, or when attachments must go out from an alias without opening a mail app. Both methods start a new conversation, not a reply. Replies to forwarded mail are covered in Reply from Aliases.

Confirming a sent email#

How do I confirm a message went out from the alias?#

With the relay address method, the sent message remains in the sent folder of the mail app it was written in, and the recipient sees the alias as the sender. The recipient can be asked to confirm arrival and to check the sender address on the message received.

With Quick Send, there is no sent folder to check, because Quick Send keeps no outbox. The recipient must be asked directly to confirm that the message arrived and that it shows the alias as the sender.

If the recipient reports that nothing arrived, work through the troubleshooting checks below before sending the message again, so the same message is not sent twice.

Troubleshooting#

Why did the send fail or bounce?#

Work through the most common causes first, in this order:

• The destination was not verified. Can Send cannot be enabled on an unverified destination. Verify the destination first, then enable Can Send. See Verifying a Destination.
• Can Send was off. If the permission was disabled and the feature was used anyway, a bounce notification email is sent. That email contains a one-click link to re-enable the permission on the relevant destination. See One-click enable from bounce email.
• The alias was not active. Sending works only from an active alias. If the alias is paused or deleted, the send does not go through. Check the alias status in the dashboard and select an active one.
• The recipient address was mistyped. Check the To field letter by letter. A single wrong character sends the message to the wrong inbox, or nowhere at all.
• The message landed in spam. The recipient should check the spam or junk folder. A new alias, or a message containing links and attachments, is more likely to be held by filters.
• An attachment broke a Quick Send message. A message over the 18 MB combined limit, or one containing a blocked file type, does not go through. Remove the file and try again.
• The problem is on the delivery side. If every check above looks correct, follow the steps in Emails not arriving.

Replies to forwarded mail#

Replies are a separate feature. When someone emails an alias and AliasFleet forwards the message, the answer should come from the forwarded message, so the thread stays together. That flow uses Can Reply, not Can Send. See Reply from Aliases for the steps. For everyday examples of one alias per site, see How Email Aliases Actually Work.