Re: [sieve][regex] Matching multiple strings in the "Received" header

2018-05-06 Thread Adi Pircalabu
On 07-05-2018 12:13, Adi Pircalabu wrote: I'm trying to use this expression in Sieve, but for some reason the filter doesn't work: require ["fileinto","regex"]; # rule:[gmail-outlook-yahoo-aol-friends] if header :regex "received" ".from.*(outbound.protection.outlook.com|.google.com|.yahoo.com|

[sieve][regex] Matching multiple strings in the "Received" header

2018-05-06 Thread Adi Pircalabu
Hi, I'm trying to use this expression in Sieve, but for some reason the filter doesn't work: require ["fileinto","regex"]; # rule:[gmail-outlook-yahoo-aol-friends] if header :regex "received" ".from.*(outbound.protection.outlook.com|.google.com|.yahoo.com|mx.aol.com)." { fileinto "I

Re: 2.3.1 Replication is throwing scary errors

2018-05-06 Thread Andy Weal
Hi all, Firstly, thank you for both your feedback and suggestions. My current work around is to use rsync to keep my standby mx "close" to up-to-date. As my servers are not commercial and production so to seek i am more than happy to carry out some tests if that would prove useful to the team.

Re: 2.3.1 Replication is throwing scary errors

2018-05-06 Thread Thore Bödecker
Hey all, I've been affected by these replication issues too and finally downgraded back to 2.2.35 since some newly created virtual domains/mailboxes weren't replicated *at all* due to the bug(s). My setup is more like a master-slave, where I only have a rather small virtual machine as the slave h

Re: 2.3.1 Replication is throwing scary errors

2018-05-06 Thread Michael Grimm
Hi Reuben, thank you for digging into this issue reported by some users, now. I wonder if there are users out there using master/master replication with 2.3.1 dovecot that do *NOT* observe the errors mentioned in this thread? Please report, please. And, pleas have a closer look for It would b

Re: 2.3.1 Replication is throwing scary errors

2018-05-06 Thread Michael Grimm
Hi Andy Andy Weal wrote > Hi all, > > New to the mailing lists but have joined up because of above 2.3.1 > Replication is throwing scary errors > > > Brief system configuration > MX1 - Main > Freebsd 11.1-Release-p9 > Hosted on a Vultr VM in Sydney AU > MTA = P

Re: 2.3.1 Replication is throwing scary errors

2018-05-06 Thread Reuben Farrelly
Ah yes. The hash I put below is wrong but the commit message I quoted was right. This is the last known working good commit, which was on Mar 6: https://github.com/dovecot/core/commit/ff5d02182573b1d4306c2a8c36605c98f217ef3b "doveadm: Unref header search context after use Fixes memory leak, fou

Re: 2.3.1 Replication is throwing scary errors

2018-05-06 Thread Aki Tuomi
Seems you got the hash wrong... You probably mean 4a1e2e8e85ad5d4ab43496a5f3cd6b7ff6ac5955, which fixes a memory leak, but does not release sync lock. Interesting if this commit fixes the issue. Looking at the sync code, where the lock is made / released, there is only one commit recently, whi

Re: 2.3.1 Replication is throwing scary errors

2018-05-06 Thread Reuben Farrelly
Hi Andy, Funny you say that - I've been testing this very problem for some time today to narrow down the commits where I think the problem started occurring. So far I have been able to roll forward to commit from git: 74ef8506dcb946acc42722683e49fdcb964eed19 >> "doveadm: Unref header searc

Dovecot fts script with solr

2018-05-06 Thread André Rodier
Hello again, I have created a parser script, a little bit more advanced than the one provided with Dovecot. The main feature is probably to index documents inside zip/rar/tgz archives... I am using Ansible, swaks and doveadm to run automatic tests for each supported content. For specific rea