Re: [sieve] Script Runtime errors via X-Headers

Tim Showalter <tjs@psaux.com> Sat, 13 October 2012 00:02 UTC

Return-Path: <tjs@psaux.com>
X-Original-To: sieve@ietfa.amsl.com
Delivered-To: sieve@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3F6821F86A8 for <sieve@ietfa.amsl.com>; Fri, 12 Oct 2012 17:02:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eO9NtGT9Ivgm for <sieve@ietfa.amsl.com>; Fri, 12 Oct 2012 17:02:16 -0700 (PDT)
Received: from smtp103.prem.mail.sp1.yahoo.com (smtp103.prem.mail.sp1.yahoo.com [98.136.44.58]) by ietfa.amsl.com (Postfix) with SMTP id D3EFE21F86A4 for <sieve@ietf.org>; Fri, 12 Oct 2012 17:02:16 -0700 (PDT)
Received: (qmail 33192 invoked from network); 13 Oct 2012 00:02:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1350086532; bh=UVezaukZm5/6OjNpu+3dUv6y5hXYs9dM99YQ4joUXHg=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=V+lwmSA7l/6dLudVoZSKpfc5UgJGW9/wmC6KdI2tDd2X/DXHWCaWuZ4hPkOQo8JJqYdtwzZq1OhzdbxkPu8QYhCHjrt0UonROS4p7RrCDnPi5ik7QscQO9fM8FzJpbQm4WrWwLVcyt7IoQsF0gWlHLLSSIOsArlpvwbYv8d5gys=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: BiARaBcVM1ltLdKxKa4_mOnU5apd5NrUvZYAPlsg.A_2CYu hIHoh3SxCZxS93WkjBsH4rFxLFthhAo1Qo8Zv4_niFn2WYuZiyBUYF1oX2ab RhYzvtlrWlLOUvYi.OYFxn8WffXSMOk4ancVOnvMkQz78O5Cwtil949vTqJT uPmFCQQXZzUwfhFalzCbzdmf26RKPAXzIrDBp8rYMBtr4.kR16bvhmmvepOM vN8UF9TDaooMVQbzJ5ANm1lUmLOo2hneTNVfAcoIjblk55Td_7hPicOHyvcT vtr2ELvlYkSAs0LItqV8iUmMbPvCSqPzAwRJCs9x3DPRMOmO9oB3slOb30VV AFMInd.ie3aNi0o386Cw3OpoaWw3d_8AaxI0BpkpuR7iIeEQPgo1_f6f8oBS QEiDfJQo6KsHYCeA.4Ae65j_nDrdfrRF6rITPRBHigBVj8IpnLUJ5wQMqHNX qCQ--
X-Yahoo-SMTP: jK5ghcGswBAlBjVhZO0ppd4-
Received: from bgai-mn(2).linkedin.biz (tjs@69.28.149.29 with plain) by smtp103.prem.mail.sp1.yahoo.com with SMTP; 12 Oct 2012 17:02:12 -0700 PDT
Message-ID: <5078AF84.6050602@psaux.com>
Date: Fri, 12 Oct 2012 17:02:12 -0700
From: Tim Showalter <tjs@psaux.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: sieve@ietf.org
References: <5078823E.8030403@gmx.net>
In-Reply-To: <5078823E.8030403@gmx.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [sieve] Script Runtime errors via X-Headers
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sieve>, <mailto:sieve-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sieve>
List-Post: <mailto:sieve@ietf.org>
List-Help: <mailto:sieve-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Oct 2012 00:02:17 -0000

On 10/12/12 1:49 PM, Thomas Schmid wrote:
> Thus I would suggest adding the following to paragraph 2.10.6 :
>
>     When an error happens, implementations MUST notify the user that an
>     error occurred and which actions (if any) were taken, and do an
>     implicit keep.
>
> +  This can be achieved by adding an "X-Sieve-Error" header containing
> +  the runtime error message to the mail.
>
> What are your thought on that?

The original target for Sieve supported a multi-user server with a 
single-instance store, such that a message to N people need only be 
stored once.  The server had already committed the message to disk 
before it was handled by filtering.

So it was too late to write the header, and as the header was 
potentially shared between multiple users, it wasn't the place to put 
the data, either.

Sneaking data into headers is a hack.  It may be the best choice for 
some implementations, but it's not what headers are for.

Tim