Skip to main content
mailkube is a single binary that sends email, manages scheduled sends, and receives webhook events on your machine. It speaks to the same REST API and the same submission host your application does.

Install

Homebrew, Scoop, a shell script, go install, or a container image.

Quickstart

From nothing installed to a delivered message.

Send an email

Bodies, attachments, templates, tags, and both transports.

Command reference

Every command and every flag.

What the CLI does

Sending is the center of it. mailkube emails send builds a message from flags, a JSON payload, or a saved template, and hands it to either the REST API or SMTP submission depending on --transport. Scheduled sends can be listed, rescheduled and canceled, individually or a whole batch at a time. mailkube webhooks listen runs a receiver on your machine so you can watch real events arrive while you are writing the handler that will consume them. Around that sit the small things that make the rest usable: guided setup, credential storage across named profiles, an environment diagnostic, and an error dictionary. mailkube dashboard prints links into app.mailkube.com, so you can jump from the terminal to domain setup, credentials, templates, or the delivery log.

Observing a send

What happened to a message arrives as a webhook event. webhooks listen receives those events on your machine, so you can watch a real delivery land while you write the handler that will consume it. Its --exit-after and --exit-timeout flags turn that listener into an assertion a CI job can make: wait for one email.delivered matching your send, and exit non-zero if it never arrives. The dashboard’s log view holds the longer history.
Every send from this tool is a real, charged message that affects your sending reputation. Commands named test and flags named --sample do not change that. Use --dry-run first, and read Sending safely before you point it at a production domain.

Reading the output

The CLI writes human output when stdout is a terminal and JSON when it is not, with no flag either way. A command you worked out at a prompt behaves correctly the moment you put it in a script or a CI job. See Scripting for the stream contract and the format flags, and Errors and exit codes for what to branch on.

Help without leaving the terminal

Eight long-form topics ship inside the binary. mailkube topic lists them, mailkube topic idempotency reads one. They cover the same ground as the pages in this section and work with no network.