similar to: Sieve not filtering

> 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

> Hi! > > Can you post doveconf -n > > Aki # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-514.6.1.el7.x86_64 x86_64 CentOS Linux release 7.3.1611 (Core) auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = sha1 first_valid_uid = 1000 mail_location = maildir:~/Maildir managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject

Op 13-2-2017 om 18:15 schreef Ben: > Hi, > > I am seeing the followin error in my logs (doveconf -n at the bottom > of this mail): > > Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp at example.com): Error: > cs3NOQ7moVj4sQXXXXX: sieve: sieve file backend: invalid option > `active=~/.dovecot.sieve' > Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp at example.com): Error:

Hi, I am seeing the followin error in my logs (doveconf -n at the bottom of this mail): Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp at example.com): Error: cs3NOQ7moVj4sQXXXXX: sieve: sieve file backend: invalid option `active=~/.dovecot.sieve' Feb 13 16:59:59 mxf dovecot: lmtp(45560, bp at example.com): Error: cs3NOQ7moVj4sQXXXXX: sieve: failed to access user's Sieve script

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

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;

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

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

Guys, I'm completely stuck, so asking for advice. My user has a sieve script which checks message header if it contains words in russian like '???? ???????????? ?????????'. Pritty simple script # rule:[??????????] if allof (header :contains "subject" "LDS (robot): ???? ???????????? ?????????", header :contains "from" "noreply at

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

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

Hello, As far I saw in archive mailing list, I am not the first person with this problem. Anyway I was not able to pass this error once the information I got from the archive it is not very conclusive for this case. I have used linear, radial and sigmoid kernels for the same data in the same conditions and everything is ok. This problem just happens with the polynomial kernel. I send the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a global sieve rule in place to filter mailing-lists. This has worked well so far. Recently however one subscriber on a list seems to create strange character set encodings in the 'From' and 'To' headers. This leads to unprocessed/unfiltered mails (no errors thrown). Is this a configuration or Pigeonhole issue (latest HG used)?

I am a bit at a loss here with Sieve (pigeonhole) and the spamtest extension. I am using Dovecot 2.1.7 (backported to Debian squeeze), which comes with Pigeonhole 0.3.0. Messages are scanned with SpamAssassin, which adds a header like X-Spam-Status: Yes, score=84.6 required=5.0 tests=? and so I configured spamtest in conf.d/90-plugin.conf like so: sieve_spamtest_status_type = score

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. Interestingly, if I remove the "if duplicate" filter, the header does get deleted as expected. I'm using the latest Dovecot 2.3.11.3 / Pigeonhole 0.5.11. Any idea why this is