IETF Logo Mail Archive

Re: [ietf-smtp] [Proposal] confusing parts of the mail system, was 250-MARKDOWN

Gilles Chehade <gilles@poolp.org> Fri, 11 January 2019 13:55 UTC

Return-Path: <gilles@poolp.org>
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 3D54A124BE5 for <ietf-smtp@ietfa.amsl.com>; Fri, 11 Jan 2019 05:55:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=poolp.org
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 JwtQofmweDk3 for <ietf-smtp@ietfa.amsl.com>; Fri, 11 Jan 2019 05:55:04 -0800 (PST)
Received: from out.mailbrix.mx (out.mailbrix.mx [212.83.129.132]) (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 13EB5124BAA for <ietf-smtp@ietf.org>; Fri, 11 Jan 2019 05:55:03 -0800 (PST)
Received: from poolp.org (localhost [127.0.0.1]) by poolp.org (OpenSMTPD) with ESMTP id 182fadbd; Fri, 11 Jan 2019 14:55:01 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=poolp.org; h=date:from:to :cc:subject:message-id:references:mime-version:content-type :in-reply-to; s=opensmtpd; bh=H+isQdJ9ks9KEJjcUV0qjNwGg5M=; b=si +kWg5EF9GghMSn9UaFUDjTvk6YMVYANnx3x89c5KiZFdaohh9xhOMJy0A75wa/kW gCXMJqLFMfZ1N3/tMVBNevOJwGEn9aTJ4hopVgxU+nmUjsA34UKs9N7rfuQmREOi fCOwOLknN7NoB+cFVF4UnLoMDPGLe48G4uXoUWPFk=
Received: from localhost (poolp.org [local]) by poolp.org (OpenSMTPD) with ESMTPA id d5f440ad; Fri, 11 Jan 2019 14:55:01 +0100 (CET)
Date: Fri, 11 Jan 2019 14:55:01 +0100
From: Gilles Chehade <gilles@poolp.org>
To: valdis.kletnieks@vt.edu
Cc: John Levine <johnl@taugh.com>, ietf-smtp@ietf.org
Message-ID: <20190111135501.GA79280@ams-1.poolp.org>
References: <20190110210727.8878F200C85075@ary.qy> <18810.1547156963@turing-police.cc.vt.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <18810.1547156963@turing-police.cc.vt.edu>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/5y-P7I0G_fg06QzuyhD9bE_7C8c>
Subject: Re: [ietf-smtp] [Proposal] confusing parts of the mail system, was 250-MARKDOWN
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: Fri, 11 Jan 2019 13:55:07 -0000

On Thu, Jan 10, 2019 at 04:49:23PM -0500, valdis.kletnieks@vt.edu wrote:
> On 10 Jan 2019 16:07:27 -0500, "John Levine" said:
> 
> > The theory is that you submit the whole message to Google and it
> > probes the recipients before it accepts the message, but now you have
> > the added issue of how to report back that receipient A can handle it
> > but recipient B cannot.
> 
> That will teach me to reply before caffeine. ;)  I was discussing the MUA-MSA
> interaction. And you'd think that somebody like me would know that stuff :)
> 
> You can receive a RCPT TO, and probe before returning a 250/550. You can cheat
> a bit if you turn on PIPELINE, then you can accept up to the DATA, and do
> probes in parallel with accepting the next RCPT before feeding back all the 2xx
> Recipient OK and 5xx Won't Work replies.
> 

Do we rename SMTP to MTP while at it ? :-)


-- 
Gilles Chehade						       @poolpOrg

https://www.poolp.org                 tip me: https://paypal.me/poolpOrg

v2.23.0 | Report a Bug | By Email