Replies always go out from the right address

The rule

Open a message and the composer is already set to the mailbox that received it. The From line is not a dropdown you have to notice; it is a consequence of which conversation you are in. Switch to a thread in another account and the sender changes with it.

The same rule holds for the rest of the composer. The signature is the one belonging to that address. The message is sent through that account’s own SMTP server, so the envelope, the headers and the SPF alignment all match the address a client already knows.

Aliases and send-as addresses

Many mailboxes receive more than one address: contact@ and hello@ landing in the same place, or a second domain pointed at an old one. Mailbind lets you add those addresses to a mailbox and verifies each one with a code sent to it, so a mailbox can only claim an address it can actually receive.

Once an alias is verified, a message that arrived at it is answered from it. The reply to someone who wrote to hello@ comes back from hello@, not from the mailbox’s primary address.

• Verification by code, so nobody can send as an address they do not control.
• A per-address signature, because a second domain usually means a second brand.
• Manual override in the composer for the rare message that genuinely has to go out from somewhere else.

Why a dropdown is not enough

Every multi-account client has a sender dropdown, and every one of them puts the burden on you to check it at the moment you are least likely to: when you are replying quickly. The dropdown defaults to something — the first account, the last used account, the primary address — and that default is wrong exactly as often as your mail is mixed.

Making the sender follow the message means the common case needs no attention at all, and the rare case is still possible. That is the whole feature, and it is the reason the product exists.

What happens to a forwarded or a shared message

Two cases deserve naming because they are where the rule earns its keep. The first is forwarding: mail that reaches you through a forward from an old address shows the address it was forwarded to in its headers, so adding that old address as a verified alias is enough to have replies leave from it. The second is a shared mailbox: a conversation in support@ is answered from support@ by every member of the team, with the shared signature, so a customer never discovers that four different people have been answering them.

There is one case Mailbind deliberately does not guess. If a message arrived at an address the mailbox does not own and cannot verify, the reply goes out from the mailbox's own address rather than from an address that would fail an SPF or DMARC check at the other end. A reply that lands in a spam folder is worse than a reply from a slightly unexpected address.

What this needs from your mailboxes

1. 1Connect each mailbox with its own IMAP and SMTP details — one account per address or group of addresses, as your provider arranges them.
2. 2Add the aliases that arrive in each mailbox and verify them with the code Mailbind sends.
3. 3Write a signature per address if they belong to different brands.
4. 4Reply as usual: the From line is already right.

Sending always goes through the account’s own provider. Mailbind never relays your mail through its own server, which is why messages keep whatever reputation, SPF and DKIM alignment that domain already has.

Common questions

Keep reading

• All features
• Shared inbox for teams
• AI email assistant
• Arabic and RTL email client
• Security
• Help: send from another address