IETF Logo Mail Archive

Re: [ietf-smtp] DSNs

John Levine <johnl@taugh.com> Sun, 26 April 2020 22:22 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 7189A3A13EC for <ietf-smtp@ietfa.amsl.com>; Sun, 26 Apr 2020 15:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 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, HEADER_FROM_DIFFERENT_DOMAINS=0.25, 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=pQaDcCET; dkim=pass (1536-bit key) header.d=taugh.com header.b=nCd6kwQ5
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 TdGOYXozfZx0 for <ietf-smtp@ietfa.amsl.com>; Sun, 26 Apr 2020 15:22:28 -0700 (PDT)
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 1398B3A13DB for <ietf-smtp@ietf.org>; Sun, 26 Apr 2020 15:22:27 -0700 (PDT)
Received: (qmail 17514 invoked from network); 26 Apr 2020 22:22: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=4467.5ea609a3.k2004; bh=b2M563s4Dph/P01fJeRPyofN+DtLz1ew1eY80Hjlr5Q=; b=pQaDcCETiAq9dghjafhveqKDMMv+bKfWfbBAhKiXbxelVKHAlZc3BSYQRPm3awYvm2YL+Q7erCLzThThi6FdGMrzcK3qyzISXIpxTSJUeyk6cKTEtnnkA1HCY+7qEv3yhC8vg9HPaXfN4wjmlwxQw8hRlnGhCtmIX5LbGbutYfkKMm7dsRIF5jW0U74rpZnVmEngCe3dwV+4vrBZ1OAEhKK1PAdCl2h2xKevqItUsr6ggiIzdhCTfUKfq68phsqc
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=4467.5ea609a3.k2004; bh=b2M563s4Dph/P01fJeRPyofN+DtLz1ew1eY80Hjlr5Q=; b=nCd6kwQ5KaqhK95Tx7/41J3bvK6h9ZzYEUQYXmjT9hiRvDDxHroP2Hlt1JPEZjqsjIBn6mg3xpKLUm6O9OX1cJ+LnuMJuySLW0ihmeKst/N0EdMBFlwJ41Oy2Og554v+mPvprtAJIXNMy6vwuXAnxthow2OcMmDaZaNAMj4xJ8xMWB8LnYGEYMQj5c3ARL7Ce3rxWMcae9jzJhKqPMm0Ch6px09DD5wVPCrhz/zJYJAaY9vxypE3GSmCw0H4ggDI
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; 26 Apr 2020 22:22:26 -0000
Received: by ary.qy (Postfix, from userid 501) id 7E1351864BA8; Sun, 26 Apr 2020 18:22:36 -0400 (EDT)
Date: Sun, 26 Apr 2020 18:22:36 -0400
Message-Id: <20200426222237.7E1351864BA8@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: mrsam@courier-mta.com
In-Reply-To: <cone.1587934924.981704.31890.1004@monster.email-scan.com>
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/HNuJpLqxPRFR82Y91B7n65ZbCH0>
Subject: Re: [ietf-smtp] DSNs
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: Sun, 26 Apr 2020 22:22:30 -0000

In article <cone.1587934924.981704.31890.1004@monster.email-scan.com> you write:
>Incoming mail is addressed to a valid mailbox. Your MTA accepts it. As such,  
>the sender already knows it is a valid recipient.
>
>I don't follow what information is getting leaked, if a second later a  
>success DSN gets sent to the sender. The sender already knows it's a valid  
>mailbox, by the virtue of the fact that the mail was accepted.

Not necessarily.  It might be forwarded, it might bounce later.

We can bikeshed forever about whether you send a success DSN if it's
delivered to a spam folder.

R's,
John

v2.23.0 | Report a Bug | By Email