Skip to main content
Send-from-alias lets you start a new message as one of your aliases, using the mail client you already use. There is no compose screen in Maski. You encode the recipient into a special address, send from your normal inbox, and Maski rewrites the message so it leaves as your alias.
Send-from-alias is in beta and available on Pro. It works only on a verified custom domain. Shared Maski domains are reply-only. Opt in to beta from your account page to enable it.

​
The address convention

To send from an alias to a recipient, combine both into one address:
The + separates your alias from the encoded recipient, and = stands in for the @ of the recipient’s address. Example. To send from shopping@mydomain.com to bob@gmail.com, address your message to:
Maski decodes the recipient, sends the message outbound as shopping@mydomain.com, and the reply comes back to your alias.

​
Why a signature is required

A fresh outbound send is only accepted when the message you send carries a valid DKIM signature aligned with its From address. Every major mail provider signs outgoing mail with DKIM, so this normally just works. If the signature is missing or does not align, Maski refuses the send rather than relaying an unverified message as your alias, and emails you to say the send did not go through. This is deliberately strict. It is the check that stops anyone else from sending as your alias.

​
When a send is refused

A send is refused if any of the following is true:
  • the alias is paused or retired,
  • the From address is not your verified destination,
  • the message has no aligned DKIM signature,
  • your plan does not include send-from-alias,
  • the feature is switched off for your account.
Replying to a message Maski already forwarded to you is separate and does not use this convention. Just reply as normal and Maski routes it back through the alias.