EHLO is an extended version of the HELO command used in the Simple Mail Transfer Protocol to initiate communication between a sending and receiving mail server. It identifies the sending server using a fully qualified domain name and signals support for extended SMTP features. Unlike HELO, which provides only basic identification, EHLO enables the server to declare additional capabilities that can be used during the email transaction.
When a connection is established, the sending server issues the EHLO command followed by its hostname. The receiving server responds with a list of supported extensions such as authentication methods, encryption protocols, message size limits, and delivery options. This exchange defines how the rest of the email session will proceed.
EHLO is the standard command in modern email systems. HELO is typically used only as a fallback when extended SMTP is not supported. Proper EHLO configuration is essential for ensuring compatibility, security, and reliable email delivery.
Advanced
EHLO enables Extended SMTP (ESMTP), allowing servers to negotiate features such as STARTTLS for encryption, AUTH for authentication, PIPELINING for performance, and SIZE declarations for message handling. These extensions are critical for secure and efficient email transmission across modern infrastructure.
The hostname used in the EHLO command must align with DNS records. Best practice requires that it matches the PTR record of the sending IP and resolves back to the same IP address via an A or AAAA record. This forward confirmed reverse DNS alignment is a strong trust signal used by receiving servers and spam filters.
In production environments, misconfigured EHLO values such as generic hostnames, invalid domains, or mismatched records can lead to connection rejection or spam classification. Mail servers such as Postfix, Exim, and Exchange allow administrators to explicitly define the EHLO identity, which should be consistent across all outbound systems and relays.
Relevance
- Enables advanced SMTP features such as encryption and authentication
- Establishes sender identity with extended capability negotiation
- Supports secure and efficient email transmission
- Improves deliverability through proper hostname alignment
Applications
- Configuring outbound mail servers to support STARTTLS and AUTH
- Aligning EHLO hostname with PTR and A records
- Enabling performance features such as PIPELINING
- Supporting modern email infrastructure and compliance requirements
Metrics
- EHLO capability negotiation success in mail logs
- TLS adoption rate for outbound email
- Authentication success rates across SMTP sessions
- Email deliverability and rejection rates
Issues
- Invalid EHLO hostname causing connection rejection
- Lack of TLS or authentication support reducing security
- Misalignment with DNS records impacting trust
- Inconsistent configuration across mail relays
Example
A mail server connects to a receiving server and sends EHLO mail.example.com. The receiving server responds with supported extensions including STARTTLS and AUTH. The sending server upgrades the connection to TLS and authenticates before sending the message. This process ensures secure transmission and improves acceptance rates.