IETF Logo Mail Archive

Re: [ietf-smtp] DSNs

John Levine <johnl@taugh.com> Tue, 28 April 2020 22:14 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 9D2D23A0A8F for <ietf-smtp@ietfa.amsl.com>; Tue, 28 Apr 2020 15:14:01 -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=m6xZtAyj; dkim=pass (1536-bit key) header.d=taugh.com header.b=jeRTGad6
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 7-BTMfHiI5XA for <ietf-smtp@ietfa.amsl.com>; Tue, 28 Apr 2020 15:13:59 -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 9CE813A0A88 for <ietf-smtp@ietf.org>; Tue, 28 Apr 2020 15:13:59 -0700 (PDT)
Received: (qmail 43836 invoked from network); 28 Apr 2020 22:13:58 -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=ab39.5ea8aaa6.k2004; bh=DHcWJI9qSFW89YW3DW6ZI4Cfht2wM1+FNBiekaUPlQI=; b=m6xZtAyjpOjMe84xPz5LByj0OeRzheFhuw/SVjWUOxyPhS6xDKE8TpR2KchOxEvD07uF6afD8Lp12okQAfjl5Kxr6Jc30/YGZcDA5KPuBy5MfnvJIur/i45iK7ZPYtEG+xUOGesmiNnQgbch4nb2z4y3oUecIn/OnnUnZVVCqvjPatLCDyB9yoXCbT+TlUVyd6HWtncDYZf6GrTmDHHdu9KSHVyUlZe2mdk4Ujv8QK/p3vV5i1cXIF6ugDr+INhc
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=ab39.5ea8aaa6.k2004; bh=DHcWJI9qSFW89YW3DW6ZI4Cfht2wM1+FNBiekaUPlQI=; b=jeRTGad6+sAYs63bxpoMmTvvv13ltmww3saPOiE4wMWzCBPNHPas3J6CbUqpCMbsO1EkL/N8Lt13zycuMkZMnIYjLzJ0UKZWwTD7aHTzb1VUBQyXSaFKO3Xiwkh9E5mNiNDwFPLSNr+rt8j6cSn1v0jP5qQv5xumqW3dnbYrASXlypvYSqHOppBqBECoZ1SxcWJeiFF2qyv1CGzU76kc6ouuO7R7+mPecn9x1klvMWCDTr2GUwONh8JBQfKEnEgi
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; 28 Apr 2020 22:13:58 -0000
Received: by ary.qy (Postfix, from userid 501) id D6FAB188397F; Tue, 28 Apr 2020 18:13:57 -0400 (EDT)
Date: Tue, 28 Apr 2020 18:13:57 -0400
Message-Id: <20200428221357.D6FAB188397F@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: mrsam@courier-mta.com
In-Reply-To: <cone.1588076349.709902.75652.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/4dZHaq-jGx9oRRAvBf9OKleebdQ>
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: Tue, 28 Apr 2020 22:14:02 -0000

In article <cone.1588076349.709902.75652.1004@monster.email-scan.com> you write:
>> In general I agree but there are still situations where an MTA (mine
>> for example) accepts a message intending to forward it somewhere else
>> and then the forward fails.  Either send a DSN or drop it on the floor
>> at that point.
>
>Well, yes. You take ownership of that message by the act of forwarding, you  
>now own it, from the point of forwarding. If you don't want to disclose the  
>forwarded-to address, that's your responsibility, so either set the sender's  
>address to <>, or to some other address where you want the bounces to go.

Huh?  If I send a DSN it includes the original delivery address but it
doesn't have to include the forwarded-to address.

R's,
John

v2.23.0 | Report a Bug | By Email