-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alex van den Bogaerdt wrote:
On Sat, Sep 03, 2005 at 07:55:16PM +0200, Julian Mehnle wrote:
Since simply conforming to RFC HELO requirements (FQDN that
resolves to connect IP) is a reasonable authentication.
Actually only EHLO is required to be a valid FQDN, HELO isn't. Read
RFC 2821 carefully.
Maybe you could be so good to provide some more hints than just an
entire RFC?
Well, if you search for something like "HELO is not required to contain a
valid FQDN", then you're out of luck. There has _never_ been such a
requirement for HELO, not even in RFC 821.
And did you read:
"Unless the different characteristics of HELO must be identified for
interoperability purposes, this document discusses only EHLO."
?
Of course I did. This statement implies that, unless explicitly specified
otherwise, all specifications of EHLO in RFC 2821 don't affect HELO. And
since there is no explicit statement saying that the semantics of HELO
should change from RFC 821, HELO is not affected by RFC 2821.
The only thing that comes somewhat close is the following:
| 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.
Note however that this includes no strict requirement for HELO.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDGft8wL7PKlBZWjsRAiGoAJ9pG6tvbfgW2p7XXeWwwpnG2zb2vACdEN89
kXmWexveBR0OEhsUJWav+Hs=
=5YEM
-----END PGP SIGNATURE-----
-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com