Re: [ietf-smtp] Endless debate on IP literals

"John R Levine" <johnl@taugh.com> Wed, 01 January 2020 16:01 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 759B1120045 for <ietf-smtp@ietfa.amsl.com>; Wed, 1 Jan 2020 08:01:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=X26OZFji; dkim=pass (1536-bit key) header.d=taugh.com header.b=DNEqVLKp
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9qk6uiYT5L7b for <ietf-smtp@ietfa.amsl.com>; Wed, 1 Jan 2020 08:01:30 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FE4D12000F for <ietf-smtp@ietf.org>; Wed, 1 Jan 2020 08:01:30 -0800 (PST)
Received: (qmail 45601 invoked by uid 100); 1 Jan 2020 16:01:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent:cleverness; s=b21f.5e0cc258.k2001; i=johnl@user.iecc.com; bh=v+ExuLJ5Ngo1WMUHEbO/QXqxIAFULK8ZoFe78ZmB1pI=; b=X26OZFjiU4Vb/R0ceRm/UKyVe/UhOOTV5BBXeTWaJEcuePpLe58MP5fVZblqaapI5S6cI5xstQKxfcEw7rk0LRttg3yK5FpgC8BhPkkesOczOBJrd6OrhGzIVhwdC6LD8uJX27KHdDhvRPcbatesK/Ch6jwgWmi9C7+JRkg+DPzmDbej1K1RO7SqDzDTndCw8gkWqZ6t7gPzRJXGrr9Nd8jnod1koTXNNb6RSXqV2pBosgfQ4DGROETZoWumrl/W
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent:cleverness; s=b21f.5e0cc258.k2001; olt=johnl@user.iecc.com; bh=v+ExuLJ5Ngo1WMUHEbO/QXqxIAFULK8ZoFe78ZmB1pI=; b=DNEqVLKpzCxSr/QTSbHRHMTVq2dVvDmPfZLz3aCobCAgv9+ZEUNJriM3IS+4jBKgY/Ct0qYo4D9k8jn7NeHgZAE/xZFkT5tCsBkpkSU8yi67xA0/kOJm0Kh4oeaTyqUHaW7ox83ovyMKES9xr3pYJdfg84USteFFAy4UyV7iQEbx0v/JtI5Mj+plteyjrvVFC+qc70naurTGnJqszEYteaVL1RtvAGG73+2LJFoS0DwEuDte3rt8Lg7SHR1/jX3O
Date: Wed, 01 Jan 2020 11:01:28 -0500
Message-ID: <alpine.BSF.2.21.99999.352.2001011101090.45428@gal.iecc.com>
From: John R Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
User-Agent: Alpine 2.21.99999 (BSF 352 2019-06-22)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/M_a-8XmWr9rpQDO4GKm8Cxb43KE>
Subject: Re: [ietf-smtp] Endless debate on IP literals
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2020 16:01:31 -0000

In article <98ba274b-5bae-eb20-cd9c-387165d9605b@dcrocker.net>,
Dave Crocker  <dcrocker@bbiw.net> wrote:
>
>> With respect to all of the low performance IoT devices mailing out
>> status reports, that's submission, not SMTP.
>...
>> We definitely need to make it clear in 5321bis that submission and
>> SMTP are different
>+1
>
>Hence, Item 2 of the items list that I posted.

I think it's stronger than your item 2.  Even if your mail sending
setup does some MTA-like things, e.g., relay messages from somewhere
else, if it can't act like a fully capable MTA, it's doing submission
and needs to relay mail through a fully capable MTA.

I'm thinking, for example, of DMA (Dragonfly Mail Agent), a small
almost MTA that I use on my small server boxes.  Even though DMA can
technically do all the things that 5321 says an MTA is supposed to do,
I have it configured to relay everything to the submission server on
my real MTA rather than trying to send mail directly.

The definition of a fully capable MTA is circular -- it's an MTA that
does the things that persaude other MTAs that it's a real MTA.  There
are no doubt people who will find that unacceptably vague, but that's
life.

R's,
John