Re: Sieve script not working

On 3/1/19 3:18 PM, Willem Offermans wrote: Dear Andrea and Cyrus friends, That is exactly the point: it was not ``stupid`` in any way. It was ignorance, which we can only avoid by improving the documentation. I blame myself for this; I'll be glad if the documentation was improved, obviously.

Re: Sieve script not working

Dear Andrea and Cyrus friends, That is exactly the point: it was not ``stupid`` in any way. It was ignorance, which we can only avoid by improving the documentation. By the way, the debug/logging question is still not answered. Debugging/logging might also enlighten the user/administrator. Wi

Re: Sieve script not working

On 3/1/19 12:31 PM, Michael Menge wrote: is the script activated? Uh, no! a user can have multiple scripts stored on the server but only one can be activated at the same time. On the filesystem there should be a "defaultbc"  which is a soft link to the active bc file. There was no such

Re: Sieve script not working

Hi Quoting Willem Offermans : Dear Michael and Cyrus friends, Where is this documented? I cannot find anything about this in https://www.cyrusimap.org/imap/reference/admin/sieve.html The example shown in section "Testing the

Re: Sieve script not working

Dear Michael and Cyrus friends, Where is this documented? I cannot find anything about this in https://www.cyrusimap.org/imap/reference/admin/sieve.html How should a user/administrator know? Pay attention to https://www.cyrusimap.or

Re: Sieve script not working

Hi Quoting Andrea Venturoli : On 3/1/19 12:04 PM, Willem Offermans wrote: (big snip on the rest) $ man timsieved TIMSIEVED(8)  TIMSIEVED(8) Just to make sure I've clarified this: the script *is* there. ls /var/imap/sieve/u/user1 user1

Re: Sieve script not working

On 3/1/19 12:04 PM, Willem Offermans wrote: > (big snip on the rest) $ man timsieved TIMSIEVED(8)  TIMSIEVED(8) Just to make sure I've clarified this: the script *is* there. ls /var/imap/sieve/u/user1 user1.sieve.bc user1.sieve.script

Re: Sieve script not working

Dear Andrea and Cyrus friends, I remember from a long time ago, that documentation with respect to sieve was sparse. It took me quite some time to set things up and to handle sieve back then. But even now I wouldn’t know how to debug the sieve process. Most of the things in the background of th

Re: Sieve script not working

On 3/1/19 11:01 AM, Merlin Hartley wrote: Is this a shared mailbox? No. Have you actually compiled the script or just put the plain text there? Did you install the file by hand or use something like timsieved? I install the scripts via sieveshell. You haven’t really given us much to

Re: Sieve script not working

Is this a shared mailbox? Have you actually compiled the script or just put the plain text there? Did you install the file by hand or use something like timsieved? You haven’t really given us much to go on… Merlin -- Merlin Hartley Computer Officer MRC Mitochondrial Biology Unit University of

Re: Sieve script not working

On 2/6/19 6:43 PM, Bron Gondwana wrote: Yeah, it's just called test.c in the sieve directory. Here's our buildscript code: ... I'm giving up on this: I cannot get to build this test binary; besides, I'm *sure* the script is correct, since it works for other 2 mailboxes. Thanks for your hel

Re: Sieve script not working

On Tue, Feb 5, 2019, at 06:20, Andrea Venturoli wrote: > On 2/2/19 8:25 PM, Bron Gondwana wrote: > > What is being written to syslog by your lmtpd? > > Absolutely nothing (apart from transient errors on the rare occasions > when I reboot the server and sendmail comes up before imapd). > > Is thi

Re: Sieve script not working

On 2/2/19 8:25 PM, Bron Gondwana wrote: What is being written to syslog by your lmtpd? Absolutely nothing (apart from transient errors on the rare occasions when I reboot the server and sendmail comes up before imapd). Is this log to be enabled somehow? There's also a sieve-test binary t

Re: Sieve script not working

What is being written to syslog by your lmtpd? Sieve failures should be logged to syslog. There's also a sieve-test binary that you can build in the Cyrus source code. I don't think it's built by default on most platforms though, we build it specially at FM. It takes a script and a raw email an

Re: Sieve script not working

On 1/20/19 3:21 PM, Andrea Venturoli wrote: On 1/20/19 12:13 AM, Nic Bernstein wrote: Andrea, It would help to know which version of Cyrus you're having difficulty with, and what setting you're using for 'unixhierarchysep'? Sorry, I obviously should have said it from the start: I'm using vers

Re: Sieve script not working

On 1/20/19 12:13 AM, Nic Bernstein wrote: Andrea, It would help to know which version of Cyrus you're having difficulty with, and what setting you're using for 'unixhierarchysep'? Sorry, I obviously should have said it from the start: I'm using version 2.5.12 on FreeBSD 11.2/amd64. I'm not u

Re: Sieve script not working

Andrea, It would help to know which version of Cyrus you're having difficulty with, and what setting you're using for 'unixhierarchysep'?  If you've recently upgraded to 3.X, for example, have you followed the instructions and converted your sieve scripts? Cheers,     -nic On 1/19/19 5:14 AM

Sieve script not working

Hello. I'm using sieve scripts (among other things) to move messages that MIMEDefang marked as spam into a dedicated folder. My scripts look like this: require ["fileinto"]; require ["regex"]; if anyof (header :regex "X-Spam-Score" "^[1-9][0-9]\.", header :contains "X-Attachment-D

Re: Sieve script ... not working?

The Hermit Hacker wrote: > > Is there anything obviously with the following sieve script? Its not > filtering, its all still being dumped to the mailbox :( The filter is not being executed due to a parse error on the require line. The discard action is MANDATORY in sieve and therefore doesn'

Sieve script ... not working?

Is there anything obviously with the following sieve script? Its not filtering, its all still being dumped to the mailbox :( - require "discard"; if header :contains "Subject" "Delivery failure" { discard; } elsif header :contains "Subject" "Postmaster notify: see transcript fo