[Top] [All Lists]

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

2012-10-12 18:56:49
Hi Thomas,

On 10/12/2012 10:49 PM, Thomas Schmid wrote:
> recently I stumbled upon a server, which returns run time errors of a
> sieve script as an X-Header. I did not find any documentation
> regarding this behavior, so I think it non standard. Never the less
> it's quite handy. Especially if you move, rename or misspell an imap
> folder.
> Such an error X-Header looks like this:
> X-Nemesis-Sieve: missing mailbox "\example"
> Is there a chance to standardize this within the Sieve RFCs? It makes
> debugging script for inexperienced users with no access to the server
> logs way easier.
> Especially since Paragraph "2.10.6. Errors" of "rfc5228" requires
> implementation to represent script errors to the user but does not
> offer any suggestions how to do that.
> What are your thought on that?

Actually, we had a discussion about this a few years ago:

I don't think adding headers was mentioned as part of that discussion, but
FWIW, the header approach is a total nonstarter for us, for two reasons:

(1) Only a *tiny* minority of users see the full message header. In fact a
   significant number of users have no idea how to get this information
   from their user agent even if they somehow knew to look for it.

   And good luck getting user agents to display additional header information
   like this by default.

(2) This approach only works when the person responsible for the sieve content
   is the same as the message recipient. In our case the two are often
   different, and moreover the chance of a sieve runtime error is strongly
   inversely correlated with the two being the same.

The somewhat feature of using a special header is that it eliminates the risk
of getting deluged with error message reports. But we have many millions of end
user sieves deployed, and we've had no reports of this happening. (And I think
it likely we would have heard if it had happened.)

sieve mailing list

<Prev in Thread] Current Thread [Next in Thread>