Re: [Extra] Meeting minutes and notes from today

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Thu, 04 January 2018 18:07 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97FEB126C89 for <extra@ietfa.amsl.com>; Thu, 4 Jan 2018 10:07:56 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.no
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 BLHPO4IGtIzc for <extra@ietfa.amsl.com>; Thu, 4 Jan 2018 10:07:55 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [80.244.248.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43245124205 for <extra@ietf.org>; Thu, 4 Jan 2018 10:07:54 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 56760FA0003; Thu, 4 Jan 2018 18:07:53 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1515089273; bh=GJN9j9JT1cg10fdP4GG4ZSLdUncCDLNdpIQqyES4tUg=; h=From:To:Subject:Date:References:From; b=o/xFCOeHSaLP9wMxMs4fe0LyTVGa7HVVVZIOvkzYqhs+Lj9n97jSMm2fNXwW/GySj BzO4ecqJ6z4acGBO1plu9+mHAr8kpIdTXYr3Z5gCrrti86wI1+jw+NOWZHm/lBUnOj fLqbTdk9xGeu6nLgPpcTMYw+ttEcAxDRPKtqpifA=
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1515089272-7408-22429/12/1817; Thu, 4 Jan 2018 18:07:52 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: extra@ietf.org, Ned Freed <ned.freed@mrochek.com>
Date: Thu, 04 Jan 2018 19:07:50 +0100
Message-Id: <POP7FOEK+etgKJuCJ9thXhV0WM4xpgCJwo6h5JvDnRc=.sha-256@antelope.email>
References: <1510734636.1704307.1173072248.27572238@webmail.messagingengine.com> <C0D8D552-4B1C-49D9-8CCC-E6F57F225C1A@glyphein.mailforce.net> <1515028094.3135331.1223576440.053F86DC@webmail.messagingengine.com> <01QNFXVO7LVS000051@mauve.mrochek.com> <2d0523cb-5b0b-4cd0-8fd5-301ccbbc4342@gulbrandsen.priv.no> <01QNG1OISUGO000051@mauve.mrochek.com>
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/sNO2L0ysz0mkb8sULV1i0SqTkW0>
Subject: Re: [Extra] Meeting minutes and notes from today
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jan 2018 18:07:56 -0000

Right. I feel that the main disconnect here is that the reject/fcc 
combination may cause one party (the site/company/...) to make a false 
representation about delivery on the instructions of another (the 
addressee).

When those two are the same, this is okayish. Lying on my 
own accord is not pretty, but it is better than lying because someone 
else told me to.

The right answer may be that reject/fcc should be 
available only when the mta owner and the script owner are the same. Or 
that may be unwarranted complexity, and the right answer is to cater to 
one of the two cases and knowingly disregard the other.

Arnt