IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Thu, 10 January 2019 21:07 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 AD77E130F3F for <ietf-smtp@ietfa.amsl.com>; Thu, 10 Jan 2019 13:07:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=am1gzs+z; dkim=pass (1536-bit key) header.d=taugh.com header.b=X57cdUo6
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 tw3SAo0GLI5n for <ietf-smtp@ietfa.amsl.com>; Thu, 10 Jan 2019 13:07:29 -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 D0F5912896A for <ietf-smtp@ietf.org>; Thu, 10 Jan 2019 13:07:28 -0800 (PST)
Received: (qmail 56860 invoked from network); 10 Jan 2019 21:07:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=de1a.5c37b40f.k1901; bh=UtaCscLDjNV5Md+4Hh6F/UsNwF/vm+yv3b23wJVSmMw=; b=am1gzs+zsLuf4W2RvVpQK6kHENF1feHbSCVCim5+2JIWyVzeAC8mue/SHiZOyml5ExIwrtjlY6Zm4DXanBox+BfrILrbKqx+uabUj0YVGoyhKhGn88tuDmrKnmU0TvaXFCZF8dRAEZM9Nr/NVSRUgDc+84cMRz6fUZ6UuE73AgNtr6LGgTvuILdqa5ynebN/Fx2ioyftsHdBr8M24rW7SyzvytGl9S4tyAVCyfev6okfh7ISnnwb7Od4+pjy3+Kj
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=de1a.5c37b40f.k1901; bh=UtaCscLDjNV5Md+4Hh6F/UsNwF/vm+yv3b23wJVSmMw=; b=X57cdUo6/bjWgDR53eFglsgklni2HFz6crkqnaNl/5AASx29PoFKaugMwT7mpEiO35ytsJpsnO+YmJE3aLgdsuj0FHlcA/1bQi6i0Uri+iL4M4VPefqROyqAH7X8IVB9OLK2aKSugNK9bgdydwXRC/C1GKNWsAFLw1TWg8KV2e9uR4dt2MDa1n3qNAlibpjol6bgiDqLzMpu2B721qT4F40o0H0w28eoFQCASfkq5k9DBOkRsG8wwXBx1/c2Pwa3
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 10 Jan 2019 21:07:27 -0000
Received: by ary.qy (Postfix, from userid 501) id 8878F200C85075; Thu, 10 Jan 2019 16:07:27 -0500 (EST)
Date: Thu, 10 Jan 2019 16:07:27 -0500
Message-Id: <20190110210727.8878F200C85075@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: valdis.kletnieks@vt.edu
In-Reply-To: <13753.1547150864@turing-police.cc.vt.edu>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/pl_EHoC4Az41cbhSl9Y2pHLKayk>
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: Thu, 10 Jan 2019 21:07:31 -0000

In article <13753.1547150864@turing-police.cc.vt.edu> you write:
>On Thu, 10 Jan 2019 11:55:53 -0800, John Bucy said:
>
>> The MSA could call ahead/cut-through, doesn't exim do that? That might also
>> allow for the mua to throw an error ui at the user if they fat-fingered the
>> recipient rather than getting a bounce back later.
>
>No.
>
>Consider this reply.  I'm in Comcast cable territory, which means that I can
>only do outbound port 25 to Comcast/Xfinity servers.  So my only realistic
>way to get this mail out is to 587 it to Google's submission servers.
>
>Now how do I "call ahead" for the cc: that's going to John Levine?

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.

I'd really rather the duct tape be applied to make external-body work
better.

R's,
John

v2.23.0 | Report a Bug | By Email