search for: tlevels

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 <-

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

# 2.2.12: /etc/dovecot/dovecot.conf # OS: Linux 3.15.4-x86_64-linode45 x86_64 openSUSE 12.3 (x86_64) Short version: 1) I filter out spam by using a dovecot sieve filter to act based on a header inserted by bogofilter 2) In some cases, sieve fails to correctly file based on this header 3) Testing with sieve-test indicates that it's testing the wrong header 4) Suggestions? Am I doing

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

E.B. schreef op 5-5-2015 om 9:40: >>>> Last two changes should fix this: >>> >>> Not yet -- this may be unrelated(?) but here is what I have >>> after installing the newest source package: >>> >>> Error: Couldn't load required plugin /usr/local/lib/dovecot/lib90_sieve_plugin.so: >>> dlopen() failed:

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]:

Hi, Something mightily weird is going on at your end. It doesn't fail here (see below). First of all, what is your configuration (output from `dovecot -n`)? Also, can you make a hex dump of the binary (using `sieve-dump -h <your-script-binary>.svbin`). See below for an example at my end. Finally, can you try to explicitly delete the binary (preferably after preserving it

Hi Stephan, On Wednesday 02 September 2020 19:59:57, Stephan Bosch wrote: > > > On 29/08/2020 21:04, Alec Moskvin wrote: > > Hello, > > > > I have a rule to always delete a header. If the message gets fileinto'd, > > the header is gone, but if it's delivered into the INBOX through > > implicit keep, the header does not get deleted. > > >

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; }

On 4/30/2015 9:15 PM, Larry Rosenman wrote: > 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", >

On 5/15/2015 4:58 PM, Chris Adams wrote: > 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

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. >

Op 13-1-2017 om 9:15 schreef Thomas Leuxner: > Hi, > > I recently noticed that some of my automatically processed mails do no longer show flags with current Dovecot builds. This used to work before, not sure what broke it or whether I used it in the wrong way. When the removeflag line is dropped *both* messages get flagged in the client, one in INBOX and one in Trash. With removeflag in

> On 17 February 2017, at 08:24, Ben <ben+dovecot at list-subs.com> wrote: > > Hi, > > 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:

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

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? > > > $ sieve-test -D -c dovecot.conf sieve message >