Re: [ietf-smtp] SMTP Reply code 500

Paul Smith <paul@pscs.co.uk> Thu, 05 March 2020 09:22 UTC

Return-Path: <paul@pscs.co.uk>
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 3E1C53A10E9 for <ietf-smtp@ietfa.amsl.com>; Thu, 5 Mar 2020 01:22:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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=pscs.co.uk
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 5BWJxbnJ02yL for <ietf-smtp@ietfa.amsl.com>; Thu, 5 Mar 2020 01:22:49 -0800 (PST)
Received: from mail.pscs.co.uk (mail.pscs.co.uk [195.224.19.137]) (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 6BC7F3A10E6 for <ietf-smtp@ietf.org>; Thu, 5 Mar 2020 01:22:48 -0800 (PST)
Authentication-Results: mail.pscs.co.uk; spf=none; auth=pass (cram-md5) smtp.auth=pscs
Received: from lmail.pscs.co.uk ([192.168.66.70]) by mail.pscs.co.uk ([10.224.19.137] running VPOP3) with ESMTPSA (TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384); Thu, 5 Mar 2020 09:22:46 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pscs.co.uk; q=dns/txt; s=lmail; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To :Content-Type:Content-Transfer-Encoding:Cc:Reply-to:Sender; t=1583399851; x=1584004651; bh=T6R2drJX/OTukFIT1yIhSS1lkt4U65iqkwvDyOjLiMM=; b=UijH5YcXrWAttO0B7zojiqi1u4ijstBIHnNccfGKb4XD8At4d5rciWiTGviReo+IfZ6c7Vwq mKrQGhN9G8CW4EGmP0OrAsK4sCEPBZl8wuwXtEnJcrDMdTnsIvCzMNO96O3HBgbb+O1bBHRY7E iael7+83zDqzFESTV4D7RBFSE=
Authentication-Results: lmail.pscs.co.uk; spf=none; auth=pass (cram-md5) smtp.auth=paul
Received: from [192.168.66.100] ([192.168.66.100]) by lmail.pscs.co.uk ([192.168.66.70] running VPOP3) with ESMTPSA (TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384); Thu, 5 Mar 2020 09:17:30 -0000
To: Geethapriya Liyanage <g.liyanage@gmail.com>, John C Klensin <john-ietf@jck.com>, ietf-smtp@ietf.org
References: <1583290845.3368.15.camel@gmail.com> <aedd19df-c406-2513-934e-4498ae159964@pscs.co.uk> <68671CA9EB93E90C8D84DE92@PSB> <1583375973.1990.8.camel@gmail.com>
From: Paul Smith <paul@pscs.co.uk>
Message-ID: <b39087aa-a015-8cd9-cce1-8c102ceca298@pscs.co.uk>
Date: Thu, 5 Mar 2020 09:17:30 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <1583375973.1990.8.camel@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
X-Authenticated-Sender: paul
X-Server: VPOP3 Enterprise V7.10 - Registered
X-Organisation: Paul Smith Computer Services
X-VPOP3Tester: 12 345
X-Authenticated-Sender: pscs
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/i9LGeBupGrveKKu2Dexra2OmbE8>
Subject: Re: [ietf-smtp] SMTP Reply code 500
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, 05 Mar 2020 09:22:51 -0000

On 05/03/2020 02:39, Geethapriya Liyanage wrote:
> Thank you very much for the reply.
>
> My doubt was, how client should handle receiving an out of rage code 
> (Eg 600).    Now it is clear, client should gently drop the connection 
> with QUIT.

Yes - there is no clue what a response code of '600' would mean. I'd 
assume it failed, and give up.

But, don't take it too far. If you got a response code such as 492 
that's not listed in any SMTP documentation, I'd treat that as any other 
4xx code and treat it as a temporary failure. Strictly, it's invalid 
because the second digit is supposed to be 0-5 according to RFC 5321, 
but the first digit is sufficient for most processing, so I'd go with that.



-- 


Paul Smith Computer Services
Tel: 01484 855800
Vat No: GB 685 6987 53

Sign up for news & updates at http://www.pscs.co.uk/go/subscribe