Re: [ietf-smtp] [ dispatch] Forced SMTP redirects

Laura Atkins <laura@wordtothewise.com> Thu, 18 March 2021 14:55 UTC

Return-Path: <laura@wordtothewise.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 388C53A2D21 for <ietf-smtp@ietfa.amsl.com>; Thu, 18 Mar 2021 07:55:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=wordtothewise.com
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 yIZY2WS4gV50 for <ietf-smtp@ietfa.amsl.com>; Thu, 18 Mar 2021 07:55:27 -0700 (PDT)
Received: from mail.wordtothewise.com (mail.wordtothewise.com [104.225.223.158]) by ietfa.amsl.com (Postfix) with ESMTP id 00E7A3A2D24 for <ietf-smtp@ietf.org>; Thu, 18 Mar 2021 07:55:26 -0700 (PDT)
Received: from [192.168.0.227] (unknown [37.228.231.27]) by mail.wordtothewise.com (Postfix) with ESMTPSA id C72AA9F149 for <ietf-smtp@ietf.org>; Thu, 18 Mar 2021 07:55:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=wordtothewise.com; s=aardvark; t=1616079325; bh=ajIk63/x/zwsQGUOwElYrkuYDIsFNHMhQ+fFWeaG82w=; h=From:Subject:Date:References:To:In-Reply-To:From; b=SEVyry4WfAHqQyoiyJSOvUsyYOy7Sn9XVkJvzgCCIp5bZVc0ztrLzLv/QRZPmjb2K d/WLQ0R8HRYRWsqqf0l7kTGThqh/i2KSeBOuIct3T7i+CUS88mrAjM820L5Ylk3mgo Dti3IamuvcrdoWV66KDlivSEmF23rWK9jKJ4VmZU=
From: Laura Atkins <laura@wordtothewise.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C9417B2F-AD79-476B-9514-5E22F27DEB7A"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Thu, 18 Mar 2021 14:55:22 +0000
References: <CAKFo7wkawgk-Yj676kE5MqK8XuebuArMexH-eOdq_Uo7ijdimQ@mail.gmail.com> <20200710015947.0BE2D1C78A2F@ary.qy> <CAKFo7w=MJBt0FdnCcOZCXZWdkd6Jinv4TqwdpefdoaCncbZH3Q@mail.gmail.com> <6AEA7D44C8037B32BC1F3810@PSB> <81d0132b-3ebf-2b0b-756b-503bb5afdb37@dcrocker.net> <8E2D8138-EE61-486A-B957-A922F0C6F4B3@dukhovni.org> <20210318003233.DC44C70A8F5D@ary.qy> <e90d22da-e124-4542-8ef6-83798f5725de@gulbrandsen.priv.no> <F5461844610EDF6715D08D1B@PSB> <503e5ae8-71a1-8c9e-33b3-5c475d0ad76f@pscs.co.uk>
To: ietf-smtp@ietf.org
In-Reply-To: <503e5ae8-71a1-8c9e-33b3-5c475d0ad76f@pscs.co.uk>
Message-Id: <C7297FCD-DA5A-43D1-972C-537171D4330F@wordtothewise.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/iAziLcz67btifoYqgpvKhTBtppk>
Subject: Re: [ietf-smtp] [ dispatch] Forced SMTP redirects
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: Thu, 18 Mar 2021 14:55:29 -0000


> On 18 Mar 2021, at 14:19, Paul Smith <paul@pscs.co.uk> wrote:
> 
> On 18/03/2021 13:51, John C Klensin wrote:
>> There are, I think, two unresolved question about the
>> interactions with extended reply codes.  One is what a client is
>> expected to do it receives an unrecognized code --either one in
>> the ranges used by SMTP/5321 or completely out of range (666
>> anyone?)-- followed by some digits and periods that might be an
>> extended code?
> 
> From our SMTP client's point of view. An *extended* status code can be anything, but the basic status codes have to be 1xx to 5xx (xx can be any non-space character - we're quite forgiving). A response of "451 8.5.1 whoopsie" would be treated as a response of 451 with text "8.2.1 whoopsie"
> 
> An invalid basic status such as '666' would be treated as a generic 5xx response. I'm not really sure what else could be done with it.
> 
> We just use the first digit of the basic status code, and pretty much ignore the extended status code. There's the *option* of doing something with it, and the user (server administrator) can set it up to do something with it, but, as far as I am aware, no one ever does, as it's too fragile, and gives negligible benefit for our customers. (For mail servers handling more mail, then I wouldn't be surprised if they do something with the extra digits, but our software is aimed at SMEs, not at Gmail-wannabees.)

MTAs that send high volumes of email do pay attention to the other digits and the extended codes. In fact, many of them do full text parsing to try and determine how they should handle future mail to that address. https://smtpfieldmanual.com is one example. 

> IME, the code details and extended codes are slightly useful for diagnostic and troubleshooting, but, not really, as most of them are only useful to the remote mail server "administrators", and in most cases those people haven't got a clue what would trigger the different codes.

The code details and extended codes are very useful for high volume senders trying to manage large bulk sends and their databases. They are parsed, and tracked and updated so that senders can follow what is happening with their sends. It is a challenge to programatically interpret the responses to manage future sends to an address. 

laura 

-- 
Having an Email Crisis?  We can help! 800 823-9674 

Laura Atkins
Word to the Wise
laura@wordtothewise.com
(650) 437-0741		

Email Delivery Blog: https://wordtothewise.com/blog