Re: Sieve not working

On Friday 15 February 2019, J Pilfold-Bagwell wrote: >    sieve        cmd="timsieved" listen="0.0.0.0:2000" prefork=0 >    sievecmd="timsieved" listen="0.0.0.0:4190" prefork=0 I think what you should to change it to sieve1cmd="timsieved" listen="0.0.0.0:2000" prefork=0 s

Re: Sieve not working

Dear jpilfold-bagwell and Cyrus friends, Now you are sure that sieve is actually listening on the mentioned ports. How about the main question? Are the scripts applied to the incoming mail? Wiel Offermans wil...@offermans.rompen.nl > O

Re: Sieve not working

Hi Willem, Once I found that you can run sieve on ports 200 and 4190 at the same time, I set it up just in case Cyrus was talking to only one of the ports. If I telnet in, I get this response. [root@mail rules]# telnet localhost 2000 Trying ::1... telnet: connect to address ::1: Connection re

Re: Sieve not working

Dear Egoitz and Cyrus friends, Check if sieve is actually listening at port 2000 as well. Wiel Offermans wil...@offermans.rompen.nl > On 18 Feb 2019, at 09:34, ego...@sarenet.es wrote: > > Hi! > > > > Could you try enabling local6.debug channel in syslog, so that you could see > additio

Re: Sieve not working

Hi! Could you try enabling local6.debug channel in syslog, so that you could see additional Sieve debugging information?. Can you then post that log? Cheers! El 2019-02-15 12:32, J Pilfold-Bagwell escribió: > Hi All, > > I have a Centos 7 box running with the latest default cyrus install fro