[Dovecot] sieve script tracing
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
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 for the actual LDA plugin.
What is your application?
Regards,
Stephan.
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 (... anyof ( ... ) ),
example #4
allof (... ),
example #4a
allof (... ),
example #5
allof (... ),
example #6
allof (... ),
example #7
allof (... ) ) { discard; }
I'd like to know which condition was the actual reason of e-mail discarding. I thought about log message.
Regards,
MU
On Sun, 05 Jun 2011 22:48:16 +0200 Maciej Uhlig <maciej.uhlig@us.edu.pl> 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. My coding skills are certainly not up to the task of writing such an application and I have not been able to locate one. I have literally spent hours debugging a logic problem with sieve scripts. It ain't fun. ☹
-- Jerry ✌ Dovecot.user@seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
Op 5-6-2011 23:16, Jerry schreef:
On Sun, 05 Jun 2011 22:48:16 +0200 Maciej Uhlig<maciej.uhlig@us.edu.pl> 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. My coding skills are certainly not up to the task of writing such an application and I have not been able to locate one. I have literally spent hours debugging a logic problem with sieve scripts. It ain't fun. ☹
Have you ever tried the sieve-test command line tool? If that is not adequate, could you provide a description of what you would need instead?
Regards,
Stephan.
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 ( ... ) ),
example #3
allof (... anyof ( ... ) ),
example #4
allof (... ),
example #4a
allof (... ),
example #5
allof (... ),
example #6
allof (... ),
example #7
allof (... ) ) { discard; }
I'd like to know which condition was the actual reason of e-mail discarding. I thought about log message.
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.
Regards,
Stephan.
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 script testing. But I'm rather interested in statistics (which rule most probably causes mail discarding).
Regards,
MU
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.
Thanks. It could be really helpful in case of script testing. But I'm rather interested in statistics (which rule most probably causes mail discarding).
I've made the vnd.dovecot.debug extension available for the LDA Sieve plugin. This allows logging debug messages to the user's personal logfile (typically ~/.dovecot.sieve.log). It's currently only explained in the sieve-test man page. This change will be included in the next release.
Regards,
Stephan.
participants (3)
-
Jerry
-
Maciej Uhlig
-
Stephan Bosch