On Fri, 2018-09-21 at 09:15 +0300, Aki Tuomi wrote:> 1. > > set mail_debug=yes, try again, and check logsThe output copied and linked to on pastiebin.com is with mail_debug=yes set. I never see the global sieve script even read.> 2. > > take one email (the whole email as source), store it as mail.eml and > use > sieve-test to find out if your script is broken.I will do that. But, the global sieve is a verbatim copy of the filter I had in my personal sieve file. I only have one filter in the global sieve: require ["fileinto"]; # rule:[Spam filter] if header :contains "X-Spam-Flag" ["YES"] { fileinto "Spam"; stop; } I am perplexed! -- Ranbir
On 9/21/18, 3:05 PM, "dovecot on behalf of Ranbir" <dovecot-bounces
at dovecot.org on behalf of m3freak at thesandhufamily.ca> wrote:
On Fri, 2018-09-21 at 09:15 +0300, Aki Tuomi wrote:
> 1.
>
> set mail_debug=yes, try again, and check logs
The output copied and linked to on pastiebin.com is with mail_debug=yes
set. I never see the global sieve script even read.
> 2.
>
> take one email (the whole email as source), store it as mail.eml and
> use
> sieve-test to find out if your script is broken.
I will do that. But, the global sieve is a verbatim copy of the filter
I had in my personal sieve file. I only have one filter in the global
sieve:
require ["fileinto"];
# rule:[Spam filter]
if header :contains "X-Spam-Flag" ["YES"]
{
fileinto "Spam";
stop;
}
I am perplexed!
Did you compile (sievec) the script?
On Fri, 2018-09-21 at 20:07 +0000, Larry Rosenman wrote:> Did you compile (sievec) the script?Yes, I mentioned this in my first post. Here are the contents of the global sieve dir: [root at mailhost global]# ls -al total 8 drwxr-xr-x. 2 root root 44 Sep 21 16:12 . drwxr-xr-x. 3 root root 19 Sep 11 12:04 .. -rw-r--r--. 1 root root 118 Sep 19 16:52 global.sieve -rw-r--r--. 1 root root 197 Sep 19 16:56 global.svbin That looks ok to me. Plus, sievec didn't complain when I ran it on global.sieve. -- Ranbir