Sieve with LDA

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Sieve with LDA

Doug Hardie
I found an email that sieve stored in Deleted Messages incorrectly.  The log messages show sieve doing that, but don't give me any indication of which sieve rule caused the problem.  I went through it manually, but didn't see anything that matched.  I seem to recall that there was a way to use sieve-test to show the rules and how they were applied, but I can't seem to get it to do that now.

-- Doug

Reply | Threaded
Open this post in threaded view
|

Re: Sieve with LDA

Jerry-146
On Sat, 16 Dec 2017 18:17:39 -0800, Doug Hardie stated:

>I found an email that sieve stored in Deleted Messages incorrectly.  The log
>messages show sieve doing that, but don't give me any indication of which
>sieve rule caused the problem.  I went through it manually, but didn't see
>anything that matched.  I seem to recall that there was a way to use
>sieve-test to show the rules and how they were applied, but I can't seem to
>get it to do that now.
>

It depends on how much info you want. Read the "man sieve-test" for more info.

sieve-test -d- "script file" "mail-file"

That will give you the most complete info. Omit the "-d-" for an abbreviated
output.

--
Jerry
Reply | Threaded
Open this post in threaded view
|

Re: Sieve with LDA

Doug Hardie

> On 17 December 2017, at 02:42, Jerry <[hidden email]> wrote:
>
> On Sat, 16 Dec 2017 18:17:39 -0800, Doug Hardie stated:
>
>> I found an email that sieve stored in Deleted Messages incorrectly.  The log
>> messages show sieve doing that, but don't give me any indication of which
>> sieve rule caused the problem.  I went through it manually, but didn't see
>> anything that matched.  I seem to recall that there was a way to use
>> sieve-test to show the rules and how they were applied, but I can't seem to
>> get it to do that now.
>>
>
> It depends on how much info you want. Read the "man sieve-test" for more info.
>
> sieve-test -d- "script file" "mail-file"
>
> That will give you the most complete info. Omit the "-d-" for an abbreviated
> output.
>

Thanks.  I got it figured out now.  The man page had me confused for awhile.  Found the logic error in my script.  Now to figure out how to remember this months from now...

-- Doug

Reply | Threaded
Open this post in threaded view
|

Re: Sieve with LDA

Stephan Bosch-2
Op 12/17/2017 om 12:22 PM schreef Doug Hardie:

>> On 17 December 2017, at 02:42, Jerry <[hidden email]> wrote:
>>
>> On Sat, 16 Dec 2017 18:17:39 -0800, Doug Hardie stated:
>>
>>> I found an email that sieve stored in Deleted Messages incorrectly.  The log
>>> messages show sieve doing that, but don't give me any indication of which
>>> sieve rule caused the problem.  I went through it manually, but didn't see
>>> anything that matched.  I seem to recall that there was a way to use
>>> sieve-test to show the rules and how they were applied, but I can't seem to
>>> get it to do that now.
>>>
>> It depends on how much info you want. Read the "man sieve-test" for more info.
>>
>> sieve-test -d- "script file" "mail-file"
>>
>> That will give you the most complete info. Omit the "-d-" for an abbreviated
>> output.
>>
> Thanks.  I got it figured out now.  The man page had me confused for awhile.  Found the logic error in my script.  Now to figure out how to remember this months from now...

If version is recent enough, you can also use:
https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#Trace_Debugging

Regards,

Stephan
Reply | Threaded
Open this post in threaded view
|

Re: Sieve with LDA

Doug Hardie

> On 17 December 2017, at 15:16, Stephan Bosch <[hidden email]> wrote:
>
> Op 12/17/2017 om 12:22 PM schreef Doug Hardie:
>>> On 17 December 2017, at 02:42, Jerry <[hidden email]> wrote:
>>>
>>> On Sat, 16 Dec 2017 18:17:39 -0800, Doug Hardie stated:
>>>
>>>> I found an email that sieve stored in Deleted Messages incorrectly.  The log
>>>> messages show sieve doing that, but don't give me any indication of which
>>>> sieve rule caused the problem.  I went through it manually, but didn't see
>>>> anything that matched.  I seem to recall that there was a way to use
>>>> sieve-test to show the rules and how they were applied, but I can't seem to
>>>> get it to do that now.
>>>>
>>> It depends on how much info you want. Read the "man sieve-test" for more info.
>>>
>>> sieve-test -d- "script file" "mail-file"
>>>
>>> That will give you the most complete info. Omit the "-d-" for an abbreviated
>>> output.
>>>
>> Thanks.  I got it figured out now.  The man page had me confused for awhile.  Found the logic error in my script.  Now to figure out how to remember this months from now...
>
> If version is recent enough, you can also use:
> https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#Trace_Debugging
>

Thanks, I'll investigate that.

-- Doug