Re: [ietf-smtp] SMTP Reply code 500

Geethapriya Liyanage <g.liyanage@gmail.com> Thu, 05 March 2020 02:39 UTC

Return-Path: <g.liyanage@gmail.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 86ECF3A092B for <ietf-smtp@ietfa.amsl.com>; Wed, 4 Mar 2020 18:39:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, 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 (2048-bit key) header.d=gmail.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 aZsO4cofdtxj for <ietf-smtp@ietfa.amsl.com>; Wed, 4 Mar 2020 18:39:33 -0800 (PST)
Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CEDA3A091C for <ietf-smtp@ietf.org>; Wed, 4 Mar 2020 18:39:33 -0800 (PST)
Received: by mail-pl1-x630.google.com with SMTP id g12so1959451plo.3 for <ietf-smtp@ietf.org>; Wed, 04 Mar 2020 18:39:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:date:in-reply-to:references:mime-version; bh=PpEYvvEgHvTdbIbvB7Pe24jHX3S/nxqpcrhmOVJDLFg=; b=n47GIrPrznGjlFC0/5KGLSJ8cXJhItPHQxJ+rL7ISkwAynYJVEnrL0V7+zqLzms+6F z3RltV2R82h++UWtRO9A1/oo8vpAiP0TTOMyPuMxOCmPjEUU2ejXkqr79Pfrfcg+jqwL EshgFc1F0Wh5UWR6Vn2/tdr/oXFoM6W2LQ2isspFxXY6bYUOcNjnX9dyKobq9Lh5DWt/ gbXyiNXV7Bj13UzLmXTj+6YVCX4h6Pf1g2euncCkqvPSJuvfLz1xEkFk5GL+V/9TV0ih McjqHbIEQLF3/8Z3gSPxFJiZFJHw08iff9OLb9BN4/Fnc817k34agSrtWwSeh/4gUbcc G6Rg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:mime-version; bh=PpEYvvEgHvTdbIbvB7Pe24jHX3S/nxqpcrhmOVJDLFg=; b=cYmvpYRfScqkXEKy5qh/MRId/B1WmgMq/BOMCzSyMrZozLdtUXin9VcESQDBYQmIrD dt7hX8fHV16AGrDBG6hO4JOa3v5li0E3mF92gpJiWUl6Du1xaUF79P+j9ng0LjqXa6wt cI4DLCEWz3WwY3K70K+vkvX1WXj/9omKbU1lX9bQzMq1B2ZBT42dxFV11LEWQqX+cygS PcsMqgcL4nYUdjsFjxG6uk7C2++rbWVv45EPBBhDsqpHq+W5FrriVsW+z8M9o0FL9NvT 4tO3Es2qtTnYSuEZCsD3jQBUyIS5Vig9ZlbaSQr95MTmFFcDCRHDu1i9+mImkUfFIycU L5XQ==
X-Gm-Message-State: ANhLgQ284WzW6jAkiBT4HOcWObK8j4GhzML4Ik/F3B37x9U2nom/KaXe eblCrWkZ2aGmvSbBuU3H8GKfAdk0
X-Google-Smtp-Source: =?utf-8?q?ADFU+vuRKtMASfEcfcO4LPHu6CDleztHII9jMRuYBbLL?= =?utf-8?q?MEYM1vD+7AJKWusdJdeq1wN3WtL/KRcKrA=3D=3D?=
X-Received: by 2002:a17:90a:7303:: with SMTP id m3mr6006283pjk.62.1583375972520; Wed, 04 Mar 2020 18:39:32 -0800 (PST)
Received: from [192.168.1.3] ([112.134.5.148]) by smtp.googlemail.com with ESMTPSA id q21sm31012915pff.105.2020.03.04.18.39.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Mar 2020 18:39:31 -0800 (PST)
Message-ID: <1583375973.1990.8.camel@gmail.com>
From: Geethapriya Liyanage <g.liyanage@gmail.com>
To: John C Klensin <john-ietf@jck.com>, Paul Smith <paul@pscs.co.uk>, ietf-smtp@ietf.org
Date: Thu, 05 Mar 2020 08:09:33 +0530
In-Reply-To: <68671CA9EB93E90C8D84DE92@PSB>
References: <1583290845.3368.15.camel@gmail.com> <aedd19df-c406-2513-934e-4498ae159964@pscs.co.uk> <68671CA9EB93E90C8D84DE92@PSB>
Content-Type: multipart/alternative; boundary="=-ApKQ4aUaFmRbE5CckA2r"
X-Mailer: Evolution 3.18.5.2-0ubuntu3.2
Mime-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/X81VMghFRCMrpafyeh_ysLWDguc>
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 02:39:35 -0000

On Wed, 2020-03-04 at 09:57 -0500, John C Klensin wrote:
> --On Wednesday, March 4, 2020 09:33 +0000 Paul Smith
> <paul@pscs.co.uk> wrote:
> 
> > 
> > A buggy SMTP server could send an invalid response to the SMTP
> > client  (ie a response not starting with a three digit number
> > beginning with 1 to 5). In that case, the SMTP client should
> > do whatever it wants to do, ranging from ignoring it, to
> > dropping the connection in disgust and reporting an error to
> > the user/administrator/log/whatever (I'd probably advocate for
> > the latter).
> In the interest of cleanliness (i.e., the fact that they are
> breaking the rules doesn't mean I should, even if I'm
> disgusted), I would probably advocate for sending a QUIT command
> prior to dropping the connection, but yes.
> 
> Certainly trying to continue a session with a server that is
> badly implemented enough, or has gotten confused enough, to send
> responses that don't start with a digit in the 1-5 range would
> be ill-advised.
> 
>    john
> 
> _______________________________________________
> 
Hello,
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. 
Thank you,
Geethapriya