Re: [sieve] On "reject" and :fcc Wed, 18 January 2017 15:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1C24E129461 for <>; Wed, 18 Jan 2017 07:37:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.101
X-Spam-Status: No, score=-5.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id x3S_npOKAJ45 for <>; Wed, 18 Jan 2017 07:37:09 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 31EBE126D73 for <>; Wed, 18 Jan 2017 07:37:09 -0800 (PST)
Received: from by (PMDF V6.1-1 #35243) id <> for; Wed, 18 Jan 2017 07:35:16 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii; Format=flowed
Received: from by (PMDF V6.1-1 #35243) id <> (original mail from for; Wed, 18 Jan 2017 07:35:12 -0800 (PST)
Message-id: <>
Date: Wed, 18 Jan 2017 07:23:46 -0800 (PST)
In-reply-to: "Your message dated Wed, 18 Jan 2017 07:07:38 -0500" <>
References: <> <> <> <> <> <> <> <>
To: Ken Murchison <>
Archived-At: <>
Subject: Re: [sieve] On "reject" and :fcc
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIEVE Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 18 Jan 2017 15:37:10 -0000

> As it turns out, the point with soon be moot w.r.t. Cyrus.  I realized
> last night that I never implemented ereject, and when I do, Cyrus will
> reject at the LMTP level and therefore no DSN or MDN.

Yeah, I was going to mention that but forgot. This demonstrates a much more
fundamental problem with this whole idea of, "I want copies of all the messages
'the system' sends on my behalf." If a message is rejected due to use policy
encoded in sieve or wherever, it's always best to do that using a 5yz code over
protocol, which obviously provides no fcc capabilities.

This is also true if the reject occurs prior to delivery and the response is
sent over SMTP. So unless you say that the use of :fcc requires local
generation of the DSN - in the process making your system generate more
blowback spam that it would otherwise - you end up in a situation where the
user only receives copies of the subset of messages that happened to require
local DSN generation for some other reason.

And that's a pretty significant violation of the least astonishment principle.

I suppose you could do a hack where you generate your own version of DSN you
assume the SMTP client is going to create and stuff that in the user's folder.
But really, isn't this whole thing getting a little silly?