[Top] [All Lists]

Re: [ietf-smtp] Private Domain Names and the EHLO/HELO Command

2013-03-27 10:18:37
I think using DNS to resolve is more reliable (but not easier) for public resolution issues. Using the socket stack API can provide more local information. We had to eventually single source all applets to use a single DNS client API to resolve these related discovery, caching, round-robin, etc, issues. SPF, DKIM, ADSP, VBR, etc, all depend on using a DNS based public discovery/resolution. The problem with socket stack functions is when OSes still use older networking protocols, such as NETBIOS, WINS/ARP, HOSTS files, as the higher precedence order for searching before going to DNS.


On 3/27/2013 10:12 AM, Tony Finch wrote:
Sabahattin Gucukoglu <listsebby(_at_)me(_dot_)com> wrote:
So in summary:

1.  Perform the usual reverse-forward-FQDN-search routine to find our "FQDN".
Easier and good enough just to use gethostname() or equivalent.

2.  If it's safe to send according to hostname rules, then send it, or

3.  Send our private IP address as an address literal.
More precisely, use getsockname() on the socket that is connected to the
server, and don't bother checking if it is private.


ietf-smtp mailing list