Re: [Dovecot] sieve script tracing

2011-06-08 Thread Stephan Bosch
On 6/6/2011 10:38 AM, Maciej Uhlig wrote: W dniu 2011-06-06 00:56, Stephan Bosch pisze: If you have a sample message, you can use the sieve-test tool for that. You can check the individual steps the interpreter takes while processing the message. Refer to the man page for more info. Thank

Re: [Dovecot] sieve script tracing

2011-06-06 Thread Stephan Bosch
Op 5-6-2011 23:16, Jerry schreef: On Sun, 05 Jun 2011 22:48:16 +0200 Maciej Uhlig articulated: {snip} I'd like to know which condition was the actual reason of e-mail discarding. I thought about log message. An actual way to step through the execution of the code is something that I have bee

Re: [Dovecot] sieve script tracing

2011-06-06 Thread Maciej Uhlig
W dniu 2011-06-06 00:56, Stephan Bosch pisze: If you have a sample message, you can use the sieve-test tool for that. You can check the individual steps the interpreter takes while processing the message. Refer to the man page for more info. Thanks. It could be really helpful in case of sc

Re: [Dovecot] sieve script tracing

2011-06-05 Thread Stephan Bosch
On 6/5/2011 10:48 PM, Maciej Uhlig wrote: W dniu 2011-06-05 11:37, Stephan Bosch pisze: What is your application? Actually it's something like this: >>> if anyof ( # example #1 allof ( ... anyof ( ... ) ), # example #2 allof ( ... anyof ( ... )

Re: [Dovecot] sieve script tracing

2011-06-05 Thread Jerry
On Sun, 05 Jun 2011 22:48:16 +0200 Maciej Uhlig articulated: {snip} > I'd like to know which condition was the actual reason of e-mail > discarding. I thought about log message. An actual way to step through the execution of the code is something that I have been waiting for, for quite awhile.

Re: [Dovecot] sieve script tracing

2011-06-05 Thread Maciej Uhlig
W dniu 2011-06-05 11:37, Stephan Bosch pisze: What is your application? Actually it's something like this: >>> if anyof ( # example #1 allof ( ... anyof ( ... ) ), # example #2 allof ( ... anyof ( ... ) ), # example #3 allof ( ... an

Re: [Dovecot] sieve script tracing

2011-06-05 Thread Stephan Bosch
On 06/04/2011 12:11 PM, Maciej Uhlig wrote: > Could it be possible to trace Sieve script using method other than > "enotify", i.e. to write a message to syslog using some action? > Not currently. There is a vnd.dovecot.debug extension, but that is only available for the command line tools and not

[Dovecot] sieve script tracing

2011-06-04 Thread Maciej Uhlig
Could it be possible to trace Sieve script using method other than "enotify", i.e. to write a message to syslog using some action? MU