On 8/7/2014 1:07 PM, Jerry wrote:
> On Thu, 07 Aug 2014 12:39:56 +0200, Stephan Bosch stated:
>
>> 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
On Thu, 07 Aug 2014 12:39:56 +0200, Stephan Bosch stated:
>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
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
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