Skip to content
Docs · Extension

Certified email from Gmail.

The Mailack Chrome extension adds a “Send certified” button to the Gmail compose window: write as usual and the message goes out through the platform, with NOM-151 evidence, status notifications and a downloadable certificate.

Chrome does not allow installing extensions directly from a website: download the zip, unzip it and load it in chrome://extensions with developer mode turned on. No coding needed; it's four clicks. Chrome Web Store publishing (one-click install) is on the roadmap.

  1. 01overview

    What the extension does

    It adds a “Mailack certified” toggle and its own send button to the Gmail compose window. On send, the message enters the Mailack evidence chain and the extension notifies you in Chrome at every important step: sent, sealed (certificate ready), bounced, or marked as spam by the recipient. The extension popup shows your sending history with live status and lets you download the certificate for sealed messages.

    Installs into GmailNotificationsDownloadable certificate
  2. 02installation

    Install the extension

    Download the zip from this page, unzip it into a folder, and open it in Chrome: go to chrome://extensions, turn on “Developer mode” (top right), click “Load unpacked” and pick the folder you unzipped. Done: the button shows up next time you compose. “Developer mode” is just Chrome's name for installing an extension from outside its store; it doesn't require any coding.

  3. 03configuration

    Connect your account

    The extension's options page (right-click its icon → Options) takes your API key and your organization ID, once. You'll find both in the Mailack portal, under “API keys”: copy them from there and paste them here. The sender must be an authorized address on a verified sending domain; if your account already has a default sender, the extension just uses it.

    API keyportal → API keys
    Organizationportal → API keys
    Senderauthorized address on your domain

    The key is stored in your own browser (never on a third-party server) and is only ever used to talk to the Mailack API.

  4. 04known limits

    What it doesn't do (yet)

    One recipient per send; the extension warns you when the compose window has several. There's no open-tracking: the trail is the evidence chain (delivery, bounce, seal), not a read receipt. And the Gmail draft isn't discarded automatically: if you don't want the duplicate, discard it yourself after sending the certified copy.

  5. 05roadmap

    Next phases

    Scheduled send, reusable templates, attached documents that certify who opened them and when, a panel with each recipient's history, and Chrome Web Store publishing.

Want it in your organization?

The extension is available to Mailack customers. Reach out and we'll enable it with your verified domain.