Re: [Extra] Sieve REJECT and :fcc [was Re: Meeting minutes and notes from today]

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Thu, 04 January 2018 21:33 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 D625012421A for <extra@ietfa.amsl.com>; Thu, 4 Jan 2018 13:33:31 -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 rC19ctMM8Rk5 for <extra@ietfa.amsl.com>; Thu, 4 Jan 2018 13:33:30 -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 167B51201FA for <extra@ietf.org>; Thu, 4 Jan 2018 13:33:29 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 1C152FA0003; Thu, 4 Jan 2018 21:33:28 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1515101608; bh=J+7pKYU8et71D0c8J6UK6lVtY+bT6+ALd24QxnPjNHg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=rAeOyVElwmtk7IwGIBNe6uLT4V4xgbpAH2eo1QuQuFoNGPoaHWht9YKUiDCrA2CnR GRFmjvG7JOsK09h6HyeFkfhH35GhRyeX+TvIJtxlQXVDDhRIE7ffK85eyjTqLF1Up7 /egrVozuZ/M9zTtUab+DYHFpBv/GDeJiyOpT9U64=
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1515101607-14443-22429/11/3; Thu, 4 Jan 2018 21:33:27 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: extra@ietf.org
Date: Thu, 04 Jan 2018 21:33:26 +0000
User-Agent: Trojita/v0.5-9-g8961725; Qt/4.8.6; X11; Linux; Devuan GNU/Linux 1.0 (jessie)
Mime-Version: 1.0
Message-Id: <4ae4f1d5-bf40-483a-ae88-befe01d3adef@gulbrandsen.priv.no>
In-Reply-To: <BE46D703-89FF-4250-BFF8-EB194729D4CF@glyphein.mailforce.net>
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> <BE46D703-89FF-4250-BFF8-EB194729D4CF@glyphein.mailforce.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/dGukR9UyQRc1WUuGzw9FgS9mrHg>
Subject: Re: [Extra] Sieve REJECT and :fcc [was Re: 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 21:33:32 -0000

Stan Kalisch writes:
> Perhaps, but, after all, reject already provides that facility. 
>  But that's not the central point of my argument in favor of 
> allowing reject to invoke :fcc.
>
> Some users have arguably (at least, certainly morally) 
> legitimate reasons to lie about the delivery of mail.

You can also argue that software has a duty to serve its user.

If the user wants to send mail claiming that 2+2=7 on Tuesdays, that the 
check is in the mail, or that he/she hadn't received that other mail, 
that's the user's business. The software's duty is to serve its master.

(But as I said in another message, sieve may serve two masters, and even if 
the software will loyally lie in the name of one master, that doesn't mean 
one of the masters should be able to force the software to lie in the name 
of the other.)

Arnt