Re: indexer-worker out of memory with vsz_limit=750 MB?!

> On May 15, 2016 at 2:48 PM Peer Heinlein > wrote: > > > > We're running 2.2.24 with fts_lucene and I wonder why indexer-working > can be out-of-memory even with > > vsz_limit=750 MB > > ?! > > Peer > > > May 15 12:14:51 dobby4 dovecot:

Re: SSL on doveadm port

> On May 15, 2016 at 4:36 PM Patrick Domack wrote: > > > > I have been attempting to setup ssl on the doveadm port. So far this > works fine, as long as the global certificate is used. > > I wanted to use a different certificate, one that machines the machine >

SSL on doveadm port

I have been attempting to setup ssl on the doveadm port. So far this works fine, as long as the global certificate is used. I wanted to use a different certificate, one that machines the machine name, instead of the generic mail certificate, but I have not been able to figure out how to

indexer-worker out of memory with vsz_limit=750 MB?!

We're running 2.2.24 with fts_lucene and I wonder why indexer-working can be out-of-memory even with vsz_limit=750 MB ?! Peer May 15 12:14:51 dobby4 dovecot: indexer-worker(u...@example.com): Fatal: pool_system_realloc(134217728): Out of memory May 15 12:14:51 dobby4 dovecot:

FTS and autoindex in a cluster?

In a dovecot replication cluster where both sides have fts_autoindex=yes we have a indexer-worker(u...@example.com): Indexed 1 messages in INBOX on BOTH sides. a) Is that okay because the duplicated message will be skipped or doesn't harm? b) Or should "autoindex" only be activated on one

Re: name of mailbox of implicit keep (was Re: Sieve extension for testing for mailbox)

Op 5/11/2016 om 8:34 PM schreef Jon Kristensen: > Steffen Kaiser writes: > >> On Tue, 10 May 2016, Jon Kristensen wrote: >> >>> Which Pigeonhole Sieve extension should I use to process/test a >>> message depending on whether the message is in a particular mailbox?