[Dovecot] Tracing sieve execution
I have just recently begun learning how to use sieve. For the most part, it works fine. The problem is that I have created some rather complicated rules. Occasionally, an e-mail will get sorted incorrectly and I am not able to easily determine what rule caused it to occur.
Is there any way or utility that I could use to actually see what rule or line in the sieve file caused the action?
-- Jerry Dovecot.user@seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
I hate it when my foot falls asleep during the day cause that means it's going to be up all night.
Steven WrightOn 04/30/2010 11:43 PM Jerry wrote:
I have just recently begun learning how to use sieve. For the most part, it works fine. The problem is that I have created some rather complicated rules. Occasionally, an e-mail will get sorted incorrectly and I am not able to easily determine what rule caused it to occur.
Is there any way or utility that I could use to actually see what rule or line in the sieve file caused the action?
"recently". So I assume you are using Dovecot v1.2.x. Pigeonhole Sieve for Dovecot v1.2 provides the sieve-test utility. Maybe it's helpful for you.
Regards, Pascal
The trapper recommends today: c01dcofe.1012717@localdomain.org
participants (2)
-
Jerry
-
Pascal Volk