Skip to content

SMTP probe

The SMTP probe sends a manually crafted SMTP command sequence to a mail server. Each command is configured individually, giving you full control over the protocol exchange — including AUTH, STARTTLS, and raw DATA body composition.

[SCREENSHOT: SMTP probe editor — host/port/SSL settings at top, command list below]

FieldDescription
HostSMTP server hostname or IP
PortServer port (common: 25, 587, 465)
SSL/TLSConnect with SSL/TLS from the start (port 465)

Each command in the sequence represents one SMTP dialogue step. Commands are sent in order and the server’s response is recorded for each.

Common command types:

CommandDescription
EHLO / HELOGreeting and capability negotiation
STARTTLSUpgrade connection to TLS
AUTHAuthenticate (PLAIN or LOGIN)
MAIL FROMSet the envelope sender
RCPT TOSet the envelope recipient
DATA / DATA_BODYOpen data phase / send message body
QUITClose the session

[SCREENSHOT: SMTP command list with several commands configured and response codes visible]

[SCREENSHOT: AUTH helper dialog — username/password fields, PLAIN/LOGIN selector, generated base64 output]

The AUTH helper generates the base64-encoded credential string for PLAIN and LOGIN auth. Click the helper icon next to an AUTH command to open it. The generated value is written directly into the command’s data field.

[SCREENSHOT: MIME composer dialog — From/To/Subject fields and body, formatted RFC 5322 output]

For the DATA_BODY command, the MIME composer helps you build a valid RFC 5322 message with From, To, Subject, and body. The composed message is written into the command’s data field.

Set an expected response code on any command. If the actual code from the server differs, the history entry is marked as failed.

[SCREENSHOT: SMTP command with assertion mismatch — warning chip on the command row]

{{variable}} placeholders are supported in the host field and in each command’s data field.

The history panel shows the full exchange for each past send. Commands are matched to history entries by their command string, so reordering or adding commands between runs does not scramble the history view.

[SCREENSHOT: SMTP history panel — expanded entry showing per-command exchanges with server response lines]