Re: RFC 5321bis / 2821ter

Paul Smith <paul@pscs.co.uk> Tue, 27 January 2009 14:10 UTC

Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0REAGLq077375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 27 Jan 2009 07:10:16 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n0REAGnp077374; Tue, 27 Jan 2009 07:10:16 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-smtp@mail.imc.org using -f
Received: from mail.pscs.co.uk (mail.pscs.co.uk [77.240.14.73]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n0REAEbP077360 for <ietf-smtp@imc.org>; Tue, 27 Jan 2009 07:10:15 -0700 (MST) (envelope-from paul@pscs.co.uk)
Received: from lmail.pscs.co.uk ([62.3.195.6]) by mail.pscs.co.uk ([77.240.14.73] running VPOP3) with ESMTP; Tue, 27 Jan 2009 14:10:12 -0000
Received: from [192.168.66.101] ([192.168.66.101]) by lmail.pscs.co.uk ([192.168.66.70] running VPOP3) with ESMTP; Tue, 27 Jan 2009 14:00:16 -0000
Message-ID: <497F1370.2080001@pscs.co.uk>
Date: Tue, 27 Jan 2009 14:00:16 +0000
From: Paul Smith <paul@pscs.co.uk>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Alex van den Bogaerdt <alex@vandenbogaerdt.nl>
CC: ietf-smtp@imc.org
Subject: Re: RFC 5321bis / 2821ter
References: <4979D903.1060705@pscs.co.uk> <E5EF288BD222F5BA20C735BD@PST.JCK.COM> <497980AA.2060706@es2eng.com> <C4ZHRHThnSMjwwDOZ03z0w.md5@lochnagar.oryx.com> <4979B5F2.9010102@pscs.co.uk> <WBwvOp9JIdw2SWc1HYscRg.md5@lochnagar.oryx.com> <4979D903.1060705@pscs.co.uk> <5.2.1.1.0.20090123140212.03ed3fb0@plus.pop.mail.yahoo.com> <51104ACCD26E8167A1B3981E@PST.JCK.COM> <497D8756.5030306@pscs.co.uk> <alpine.LSU.2.00.0901261913140.4795@hermes-2.csi.cam.ac.uk> <497ED51D.9040407@pscs.co.uk> <alpine.LSU.2.00.0901271130470.4546@hermes-2.csi.cam.ac.uk> <497EF204.10304@pscs.co.uk> <alpine.LSU.2.00.0901271143290.4546@hermes-2.csi.cam.ac.uk> <497EFF0E.20206@pscs.co.uk> <B21227ADC4C74BB7A9C792ED8386F1A3@vandenbogaerdt.nl>
In-Reply-To: <B21227ADC4C74BB7A9C792ED8386F1A3@vandenbogaerdt.nl>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Authenticated-Sender: paul
X-Server: VPOP3 Enterprise V2.6.0e - Registered
X-Organisation: Paul Smith Computer Services
Sender: owner-ietf-smtp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smtp/mail-archive/>
List-ID: <ietf-smtp.imc.org>
List-Unsubscribe: <mailto:ietf-smtp-request@imc.org?body=unsubscribe>

Alex van den Bogaerdt wrote:
>
>> I would argue that 'EHLO
>> mailserver.domain.com' is more useful than 'EHLO [192.168.1.1]' even
>> though the former is incorrect, and the latter correct (according to RFC
>> 5321) with dynamic IP/NAT.
>
> IMHO 192.168.1.1 is not an internet IP address. And that is a
> requirement.
>
I'm sorry, but that can't be the case.

Otherwise, how does Thunderbird send mail to a local mail server on a
private network? It can't, because it hasn't got an Internet host name,
or an Internet IP address, so can't issue a valid EHLO command.
Similarly, how does ANY SMTP client behind a NAT router with dynamic IP
(ie pretty much any home user) send a message anywhere? If what you say
is the case, then that is cutting off half the world from the SMTP network!

As far as I can see RFC 5321 doesn't say it has to be a routable IP
address to be used in an address literal.

As far as I am aware, RFC 4409 doesn't relax the requirements of RFC
2821/5321 for the EHLO parameter, so 'use message submission' is not the
answer.

-- 
Paul Smith

VPOP3 - POP3/SMTP/IMAP4/Webmail Email server for Windows