Thu, 7 Aug 2014 06:22:01 -0400 I am running Pigeonhole version 0.4.3 on a FreeBSD 10 machine. How do I actually trace which rule in my sieve file is causing a specific action on a specific email. Other then eliminating each rule one by one and rerunning the script to isolate it, how can I discover what rule is causing the problem? Thanks! -- Jerry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: not available URL: <http://dovecot.org/pipermail/dovecot/attachments/20140807/1fa863a6/attachment.sig>
On 8/7/2014 12:24 PM, Jerry wrote:> Thu, 7 Aug 2014 06:22:01 -0400 > > I am running Pigeonhole version 0.4.3 on a FreeBSD 10 machine. How do I > actually trace which rule in my sieve file is causing a specific action on a > specific email. Other then eliminating each rule one by one and rerunning the > script to isolate it, how can I discover what rule is causing the problem?You can use the sieve-test tool for that. man sieve-test Regards, Stephan.