search for: tlevel

Hello,I am using xyplot to try and create a conditional plot. Below is a toy example of the type of data I am working with slevel <- rep(rep(c(0.5,0.9), each=2, times=2), times=2) tlevel <- rep(rep(c(0.5,0.9), each=4), times=2) noutliers <- rep(rep(c(2,4), times=4), times=2) analysis <- as.factor(rep(c('uv', 'mv'), each=8)) cp <- c(0.9450,0.9525,0.9425,1.0000,0.9425,0.9410,0.900,0.800,0.9050,0.9020, 0.9040,0.9140,0.9400,0.9430,1.000,0.800 ) area &l...

On 24/09/2018 13:35, Stephan Bosch wrote: > You can enable `-d -' and `-t - -Tlevel=matching' as well. $ sieve-test -D -d - -t - -Tlevel=matching -c dovecot.conf sieve message sieve-test(james): Debug: Effective uid=1001, gid=10, home=/home/james sieve-test(james): Debug: maildir++: root=/path/to//james/Maildir, index=, indexpvt=, control=, inbox=/path/to//james/Maildir, alt...

Once upon a time, Stephan Bosch <stephan at rename-it.nl> said: > You can check the handling of a particular message yourself using the > sieve-test tool (there is a man page for it). By specifying the `-t - > -Tlevel=matching` options, you'll get detailed information on why a > particular decision is made. Hmm, that's weird. sieve-test says it would store the message into the Spam folder (as expected), but it was definitely delivered to INBOX. > Without insight in your configuration (output fro...

...contents of the final "Subject" header in the test on line 3. In the second test, on line 6, it uses a different and correct value for the same header! But too late to help as the first test was the one it should have had a match on. === begin session === $ sieve-test -t trace2.log -Tlevel=matching test.sieve message.2 Performed actions: * store message in folder: INBOX Implicit keep: (none) sieve-test(gowen): Info: final result: success $ cat trace2.log ## Started executing script 'test' 3: header test 3: starting `:contains' match with `i;asc...

On 24/09/2018 11:51, Stephan Bosch wrote: > Can you try with the sieve-test command-line tool, in particular with > trace debugging enabled? Thank you for the debugging tip, is this useful? $ sieve-test -D -c dovecot.conf sieve message sieve-test(james): Debug: sieve: Pigeonhole version 0.5.3.rc1 (716b1b49) initializing sieve-test(james): Debug: sieve: include: sieve_global is not set;

> What I did when encountering a similar issue was to take one of the messages from INBOX that should have been moved elsewhere and use sieve-test on it: > > sieve-test -Tlevel=matching <sieve source file> <message file> > > That generates a lot of output as it goes through every line of the sieve file and shows the actual values that are used for the tests. However, it pointed out my problem quite clearly. > Thank you for this. Actually, after man...

...d a snap shot link at the top that wasn't built with the > 2nd change? > > I put 2nd change in manually (its only one liner) rebuilded and after install..... > same error with recv(MSG_PEEK) Did you restart Dovecot? Also, can you try running the script through `sieve-test -D -t - -Tlevel=matching` (see man page). Regards, Stephan.

I'm running CentOS 7.1 with Dovecot 2.2.10 (CentOS packaged version). I have Postfix feeding messages to Dovecot for local delivery via LMTP, and I have Amavisd for spam filtering. For messages above a certain threshold, Amavisd adds the "X-Spam-Flag: YES" header, and I file that into the Spam folder using a default (system-wide) sieve script (there aren't any per-user sieve

Hi, I have copied accross a known-good sieve file from a working server and its not filtering. Everything just gets chucked into INBOX. doveconf-n at the bottom of this mail Feb 17 16:05:20 server postfix/smtpd[51562]: 7FA5E12CBBC: client=unknown[192.168.167.57] Feb 17 16:05:23 server postfix/cleanup[51565]: 7FA5E12CBBC: message-id=<> Feb 17 16:05:23 server postfix/qmgr[45471]:

...ipt-binary>.svbin`). See below for an example at my end. Finally, can you try to explicitly delete the binary (preferably after preserving it elsewhere) so that it is guaranteed to be created fresh? That should not matter, but you never know. ## Success at my end: $ sieve-test -D -d - -t - -Tlevel=matching ~/frop.sieve ~/message.eml sieve-test(stephan)<27390><>: Debug: Loading modules from directory: /usr/lib/dovecot/modules sieve-test(stephan)<27390><>: Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so sieve-test(stephan)<27390><>: Debu...

...6 fileinto :create "Trash"; 7 stop; 8 } + tee test.msg To: me at example.com From: someone at example.com Subject: Test Message Message-Id: <8500 at example.net> Date: Thu, 20 Aug 2020 00:21:24 +0000 (UTC) X-Bad-Header: DELETE ME Hello world + sieve-test -CDe -t- -Tlevel=matching -Tdebug -l maildir:maildir mini.sieve test.msg sieve-test(alec): Debug: sieve: Pigeonhole version 0.5.11 (d71e0372) initializing sieve-test(alec): Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. sieve-test(alec): Debug: sieve:...

Hi list, I tried to load the package SAGx and failed because it complains it's looking for the Biobass which is not there. Then I looked up the package list and Biobass is not found. I'm trying to run the Jonckheere-Terpstra test and from what I see in the R archive, SAGx is the only place it's been implemented. > library(SAGx) Loading required package: multtest Loading required

I have a rule that sends all mail from root to a mailbox, but I want it to NOT send mail from mailing-lists there. if allof (address :contains :localpart "From" "root", not anyof(exists ["List-Id","List-ID","Mailing-List", "X-List-Name","List-Post"])) { fileinto "root-mail"; stop; }

...quot;X-List-Name","List-Post"])) > { > fileinto "root-mail"; > stop; > } > > > What am I missing in the AnyOf part? Or am I totally messed up? A trace of the script shows the following for the provided example message: " $ sieve-test -t - -Tlevel=matching ~/script.sieve ~/message.eml ## Started executing script 'script' 3: address test 3: starting `:contains' match with `i;ascii-casemap' comparator: 3: extracting `From' headers from message 3: parsing address header value `m.de.groot <m.de.gr...

...essage. There > are multiple From: and Subject: headers. Would that cause sieve to > "punt" on the message (but not log anything about it)? You can check the handling of a particular message yourself using the sieve-test tool (there is a man page for it). By specifying the `-t - -Tlevel=matching` options, you'll get detailed information on why a particular decision is made. Without insight in your configuration (output from `dovecot -n`) and an example of a message that is mishandled, I cannot tell you more. Regards, Stephan.

On 5/15/2015 5:56 PM, Chris Adams wrote: > Once upon a time, Stephan Bosch <stephan at rename-it.nl> said: >> You can check the handling of a particular message yourself using the >> sieve-test tool (there is a man page for it). By specifying the `-t - >> -Tlevel=matching` options, you'll get detailed information on why a >> particular decision is made. > Hmm, that's weird. sieve-test says it would store the message into the > Spam folder (as expected), but it was definitely delivered to INBOX. BTW, did you consult your logs for any er...

...} > > # 2.2.devel (01867a4): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.devel (3c071a4) > # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 That should just work. I tested this with the indicated versions using sieve-test and an empty user account: $ sieve-test -e -t - -Tlevel=matching ~/frop.sieve ~/message.eml ## Started executing script 'frop' 6: address test 6: starting `:is' match with `i;ascii-casemap' comparator: 6: extracting `From' headers from message 6: parsing address header value `User <user at example.com...

...I have copied accross a known-good sieve file from a working server and its not filtering. Everything just gets chucked into INBOX. What I did when encountering a similar issue was to take one of the messages from INBOX that should have been moved elsewhere and use sieve-test on it: sieve-test -Tlevel=matching <sieve source file> <message file> That generates a lot of output as it goes through every line of the sieve file and shows the actual values that are used for the tests. However, it pointed out my problem quite clearly.

On 2017-02-18, Ben <ben+dovecot at list-subs.com> wrote: > >> What I did when encountering a similar issue was to take one of the messages from INBOX that should have been moved elsewhere and use sieve-test on it: >> >> sieve-test -Tlevel=matching <sieve source file> <message file> >> >> That generates a lot of output as it goes through every line of the sieve file and shows the actual values that are used for the tests. However, it pointed out my problem quite clearly. >> > > Thank you for this....

You can enable `-d -' and `-t - -Tlevel=matching' as well. Op 24-9-2018 om 13:34 schreef James: > On 24/09/2018 11:51, Stephan Bosch wrote: > >> Can you try with the sieve-test command-line tool, in particular with >> trace debugging enabled? > > Thank you for the debugging tip, is this useful? > > &gt...