Skip to main content
Any application that already speaks SMTP can send through mailkube without code changes. Point your client at the mailkube submission server and authenticate with an SMTP credential.

Choosing SMTP or REST

  • Use SMTP when you have existing software, a framework mailer, or a tool that already sends over SMTP. It’s the fastest way to route that mail through mailkube.
  • Use the REST API when you’re writing application code and want a simple JSON request, a message id in the response, and structured errors. Scheduled sending is a REST-only feature: an SMTP submission is always transmitted right away.
Both send from the same verified domains and share the same plan limits.

How a send works

1

Connect

Open a connection to smtp.mailkube.com on port 587 and upgrade to TLS with STARTTLS. See Connection.
2

Authenticate

Authenticate with your SMTP credential (username and password). See Authentication.
3

Send

Submit the message. The From domain must match the domain your credential is bound to.
If a step fails, the server replies with an enhanced status code that tells you what went wrong. See Error codes.

A send on the wire

swaks runs those three steps in one command and prints the whole session, which makes it the tool to reach for when a client is misbehaving and you need to see what the server actually said:
An accepted message ends the transcript with a queue acknowledgment:
That id is an internal queue reference. The platform message id and the delivery outcome arrive through webhook events.