Settings
Port 587 is the standard message submission port: the client connects, then upgrades to TLS with
STARTTLS before authenticating. The server refuses authentication on an unencrypted connection (524 5.7.11). Your credentials and message only ever travel over an encrypted channel.
Session
TheEHLO response advertises PIPELINING, ENHANCEDSTATUSCODES, 8BITMIME, SMTPUTF8, and STARTTLS. A connection accepts up to 5,000 recipients across all its messages, and every RCPT TO counts, including an address refused as invalid. An idle connection is closed after 1 minute, and processing after DATA has 5 minutes to complete. Message size and recipient count are capped by your plan; see Plans & limits.
An accepted message is acknowledged with a reply of the form 250 OK ids=<queue id>. That id is an internal queue reference, not the message’s Message-ID; the platform message id is exposed on the REST API and in webhook events.
Your message is delivered with a Date header set to the time mailkube relays it, and with the Message-ID mailkube assigned. Values your client wrote in either header are replaced.
Connection limits
Both limits below apply per source IP, not per credential. Behind a NAT gateway or a Kubernetes cluster that source IP is your shared egress address, so everything sending through it draws on one budget.
A client over either limit sees the connection close before the greeting, with no SMTP reply.
Keep your pool at or under 20 connections and reuse each one until it reaches 5,000 recipients, rather than opening a connection per message.
Replies at each limit
The session limits answer with these replies.<host> is the server name from the greeting.
A
451 4.4.5 means the message was not accepted, so send it again. A large message addressed to many recipients takes the longest to process, so splitting its recipients across messages keeps it inside the window.
Reading the EHLO response
swaks can open the session, negotiate TLS, and stop there, which is the quickest way to confirm the route and the certificate before you wire up a client:STARTTLS upgrade, and the certificate the server presents. Nothing is authenticated and nothing is sent.
Sample configuration
Most mailers accept these fields directly:From uses your credential’s verified domain. Server replies use enhanced status codes.