similar to: Problem with sieve not triggering randomly?

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

Once upon a time, Stephan Bosch <stephan at rename-it.nl> said: > 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`

Once upon a time, Chris Adams <cma at cmadams.net> said: > I can confirm that a message with multiple Subject: and multiple From: > headers does not get filed correctly into the Spam folder. The > sieve-test tools shows the correct action, but when the message comes in > via LMTP, it goes into INBOX. Okay, digging some more, it looks like something in sieve is overwriting the

On 5/19/2015 10:00 PM, Chris Adams wrote: > Once upon a time, Chris Adams <cma at cmadams.net> said: >> Okay, digging some more, it looks like something in sieve is overwriting >> the wrong thing when it gets messages with some headers (at least From: >> and Subject:) repeated. I enabled the vnd.dovecot.debug sieve plugin, >> and used this sieve script: > And I

Once upon a time, Chris Adams <cma at cmadams.net> said: > In the several cases I looked at, the Spam folder exists, is > getting most spam-flagged messages filed into it, it just seems to be > something about some messages (for example, got a bunch of copies of > this particular spam to different users and they all went to INBOX > instead of Spam). I can confirm that a

Once upon a time, Chris Adams <cma at cmadams.net> said: > Okay, digging some more, it looks like something in sieve is overwriting > the wrong thing when it gets messages with some headers (at least From: > and Subject:) repeated. I enabled the vnd.dovecot.debug sieve plugin, > and used this sieve script: And I guess something is re-parsing them at some point? The following

Once upon a time, Stephan Bosch <stephan at rename-it.nl> said: > You're using Dovecot 2.2.10, which is quite old. I remembered a bug like > this, but I had to look it up. This is the original bug report: Ah, sorry for taking your time on an old bug. For most of my servers, I try to use the RHEL/CentOS-provided packages where practical (because with over 100 servers running a

I have several recently-installed CentOS 7 servers that keep having systemd-journald corruption (which stops ALL logging, including syslog). Interestingly, they are all spam-scanning servers running amavisd-new (so could be some particular pattern is triggering it). Is there a "supported" way to just cut systemd-journald out of the picture and have log entries go straight to rsyslogd?

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

Once upon a time, Kenneth Porter <shiva at sewingwitch.com> said: > How would you implement the section here titled "Sendmail > workaround" using Postfix? http://www.postfix.org/postconf.5.html#recipient_delimiter -- Chris Adams <linux at cmadams.net>

Once upon a time, Kenneth Porter <shiva at sewingwitch.com> said: > Perfect. I think the only other significant customizations I have > are lines to use the MIMEDefang and OpenDKIM milters. When last I > looked into migrating, I recall that Postfix handled milters just > fine. Milters work a little different under postfix IIRC... I haven't tried them (which is a little sad,

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

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;

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=

hey folks, trying to migrate my faithful old centos6 server over to centos 7 and as part of my email server, I have amavisd, clamd, postfix, etc.. The amavisd seems to be failing with some funky (systemd) error.. Mar 6 11:39:03 monster-new systemd: amavisd.service failed. Mar 6 11:39:03 monster-new systemd: amavisd.service holdoff time over, scheduling restart. Mar 6 11:39:03 monster-new

A new user to linux, Centos 7 and CWP the following is what I get when I try to start my AMaViS (A Mail Virus Scanner) amavisd.service - Amavisd-new is an interface between MTA and content checkers. Loaded: loaded (/usr/lib/systemd/system/amavisd.service; disabled; vendor preset: disabled) Active: failed (Result: start-limit) since Tue 2018-03-06 17:01:19 WAT; 33s ago Docs:

Hi, I have a sieve filter for a mailbox with amavisd-admin mails. if header :regex "Subject" "^INVALID HEADER" { fileinto "INVALID HEADER"; } After the upgrade to dovecot 2.1.12 this filter doesn't work for some (16) messages with this subject. For 424 messages it worked correct. Any ideas where to look? Bye Daniel

Well, in part we will see if you get this and I get the return. I JUST launched my new mail server after a few miscues. Actually the OS is Redsleeve6, which is the arm port of Centos 6, and perhaps some of my problems may come down to porting problems. But first, it may be that despite my testing, I missed something in the configurations. First clamd problems: Nov 19 08:09:54 z9m9z

Hello all, My /etc/group is not quite in order (a long story), and now I need to correct privileges right here and there. I would ask someone who has amavisd-new to show me the corresponding listing as this: [root at mail amavis]# ls -l /var/amavis total 20 -rw-r----- 1 amavis 500 0 Oct 13 15:05 amavisd.lock -rw-r--r-- 1 amavis mail 5 Oct 13 11:06 amavisd-milter.pid srwxr-xr-x 1 amavis