Connect mailboxes that sign in with a username or API key
The email connect form now separates the sign-in from the sender identity — use a login username or API key that differs from your From address, add a From name, and route replies elsewhere with Reply-to.
Your email channel's sign-in and sender identity are now separate — so mailboxes and mail services that authenticate with a username or API key work too.
What's new
- Sign in with what your provider gives you — the connect form's "Email / username" field now accepts whatever your mail server signs in with: your address, a plain username, or an API key. It no longer has to be an email address.
- Choose the From address recipients see — set a "From email" when it differs from your login (common with transactional mail services). Leave it blank and it simply uses your username, exactly as before.
- Put a name on your emails — an optional From name shows recipients "Acme Support" instead of a bare address.
- Route replies anywhere — an optional Reply-to sends responses to a different mailbox, like a shared help alias.
- Change it later — the From name and Reply-to are editable any time from the channel's new Sender identity panel under Settings → Channels.