Mail server's SMTP greeting does not conform to the protocol
What this check looks for
Your mail server's opening greeting is not shaped the way the standard requires — it is over-long, contains characters it should not, or does not start with a reply code. Strict senders may refuse to continue.
Why it matters
A malformed greeting is usually a misconfigured banner or a device in front of the server rewriting traffic. Some senders abandon the connection, and a greeting carrying control characters can corrupt whatever logs or displays it.
When the check passes, your report says: “The SMTP greeting is shaped the way the standard requires”.
What it costs your score
When this check fails it removes 3 points from your Email transport score, before the status, confidence and repeat multipliers are applied. Email transport carries a weight of 8 in the overall score.
It shares the email-transport.smtp-tls family ceiling of 40 points: however many findings that family produces, together they cannot remove more than that from Email transport. One underlying problem showing up in several places is still one problem.
- Severity
- low
- Default confidence
- confirmed
- Status when triggered
- warn
- Deduction
- 3 points
- Family cap
- email-transport.smtp-tls · 40
- Category
- Email transport
- Module
- Email smtp tls
- Fix owned by
- mail provider
- In the ruleset since
- 2026.09
How to fix it
Set a conforming SMTP banner on ‹mx host›.
A greeting that breaks the protocol can cause strict senders to abandon the connection.
Set the banner to the server's own hostname and nothing surprising: Postfix
smtpd_banner = $myhostname ESMTP.Keep it well under 512 characters and free of tabs, newlines and non-ASCII characters.
If a firewall or mail gateway sits in front of the server, check whether it is rewriting the greeting.
How to confirm it worked
nc ‹mx host› 25 — the first line should read like
220 ‹mx host› ESMTP.
# Postfix (main.cf)
smtpd_banner = $myhostname ESMTPA named slot like ‹domain› — and the braces left in the configuration below — is filled in with your own values when this rule appears on a report.
Remediation by platform
smtpd_banner = $myhostname ESMTPTechnical detail
The greeting from ‹mx host› was ‹banner›. ‹banner issue› RFC 5321 §4.2 requires a reply to begin with a three-digit code, and §4.5.3.1.5 limits a reply line to 512 octets including the CRLF. dotvitals strips control characters and truncates before storing or displaying anything a mail server sends.
Standards and references
- RFC 5321 §4.2 — SMTP Replies § 4.2
- RFC 5321 §4.5.3.1.5 — Reply line size § 4.5.3.1.5
Test this on your domain
Run the check that produces this finding, on its own, against any domain.
Other email smtp tls checks
- Mail server's TLS certificate has expired or is not yet valid
- Mail server's certificate does not cover its own hostname
- Mail server's TLS certificate does not verify
- Mail server does not offer STARTTLS
- Mail server does not accept connections on port 25
- SMTP transport security was not tested
- STARTTLS is advertised but the handshake does not complete
- Mail server negotiates a deprecated TLS version