Knowledge base
Signature
Several sign-offs on each address you send from, with one picked for each message.
Details
- Written as HTML on the Signature tab of an address under Settings → Addresses, with a preview beside the box. A signature is the one part of a message people want control of to the tag (a logo, a disclaimer, a table of links), and a rich-text box that quietly drops what it cannot model is worse than a field showing exactly what will be sent.
- It goes on at the point every send path meets, so mail from the composer, the assistant, a connected app and the REST API are all signed the same way. The old footer was appended in the browser, which meant a message sent through the API carried nothing at all.
- On a reply or a forward it sits above the quoted message rather than under it. The composer marks the spot, because by the time the body is sent the “On … wrote:” line is already part of it and the end of the body is no longer the end of what you wrote.
- Leave it empty and a one-line “Sent via Nextmail” goes out instead, and the two are alternatives, never both. Turning that switch off as well is how you send mail with nothing underneath it.
- Links, images, tables and inline styling survive; scripts, event handlers,
data:links and anything that could cover the message are removed when you save, so what the preview shows is what the recipient gets. Inline styling in outgoing mail did not survive at all before this, including our own footer’s. - Any one message can carry another signature, or none. The composer’s tool row carries a signature control beside scheduling and attaching. It lists the signatures of the address in From, the one-line “Sent via Nextmail” when the address has no default, and No signature, and the choice covers that message only. It is deliberately not sticky: dropping a sign-off from one reply says nothing about the next. Scheduled and undo-window sends carry the decision through the queue with them, so a message you disarmed on Monday is still unsigned when it goes on Wednesday.
- Each address holds its own list of signatures, and there is none for the whole workspace or for your account. Open the address under Settings → Addresses and use its Signature tab: New signature adds one, each has a name, and Defaults says which one new mail starts with and which one replies and forwards start with, so a full sign-off can open a conversation and a short one can continue it. An address with no default goes out with the one-line footer instead. A catch-all has its own Signature tab for the addresses it caught, and a new address on its domain starts from a copy of its signatures. The signatures belong to the ADDRESS: everybody who sends from it signs with them, including people who never opened the page. The composer shows the signature of the address in From and swaps it when you change From. To make addresses match, Copy puts the signature on the clipboard as formatted text, Paste replaces the box with the clipboard, Copy from… fills it with a signature of another address, and Apply to other addresses adds the signature you are editing to each address you tick, replacing the one with the same name there.
- Members can change the signature of the addresses they may send from. A catch-all’s signature takes permission to change workspace settings, and so does tracking.
- On the REST API it is
/signatures: GET lists them, POST adds one, PATCH and DELETE/signatures/{id}change and remove one, and POST/signatures/{id}/copyputs one on other addresses. On the SDK it issignatures.list,get,create,update,deleteandcopy, and on the MCP serverlistSignatures,createSignature,updateSignature,deleteSignatureandcopySignature. A send picks a signature withsignatureId, and thesignaturesetting of an address is the HTML of its default for new mail.
Google Workspace
Fastmail