From: Mariano Cunietti (no email)
Date: Mon Oct 03 2005 - 06:07:32 EDT
Hi,
after setting up my "reject_non_fqdn_hostname", I looked around to see
what RFCs mandate about HELO syntax, and I did find this:
RFC 821:
HELLO (HELO)
This command is used to identify the sender-SMTP to the
receiver-SMTP. The argument field contains the host name of
the sender-SMTP.
The receiver-SMTP identifies itself to the sender-SMTP in
the connection greeting reply, and in the response to this
command.
This command and an OK reply to it confirm that both the
sender-SMTP and the receiver-SMTP are in the initial state,
that is, there is no transaction in progress and all state
tables and buffers are cleared.
RFC 2821:
4.1.1.1 Extended HELLO (EHLO) or HELLO (HELO)
These commands are used to identify the SMTP client to the SMTP
server. The argument field contains the fully-qualified domain name
of the SMTP client if one is available. In situations in which the
SMTP client system does not have a meaningful domain name (e.g., when
its address is dynamically allocated and no reverse mapping record is
available), the client SHOULD send an address literal (see section
4.1.3), optionally followed by information that will help to identify
the client system. The SMTP server identifies itself to the SMTP
client in the connection greeting reply and in the response to this
command.
There's no point that states an SMTP client should mandatorily give an FQDN.
Can anybody address me to any resource I can eventually look at?
TIA
Mariano
-- ------------------------- Mariano Cunietti System Administrator Enter S.r.l. Via Stefanardo da Vimercate, 28 20128 - Milano - Italy Tel. +39 02 25514319 Fax +39 02 25514303 www.enter.it - www.enterpoint.it PGP Key: http://www.mennox.net/pgpkey --------------------------- Gruppo Y2K - www.gruppoy2k.it
|
|
|