similar to: v2.2.17 release candidate 2 released

http://dovecot.org/releases/2.2/dovecot-2.2.17.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.17.tar.gz.sig A few director improvements since RC2, some fixes and a new plugin: http://wiki2.dovecot.org/Plugins/QuotaClone * Dovecot no longer checks or warns if a mountpoint is removed. This was causing more trouble than it was worth. Make sure that all the mountpoints that Dovecot

http://dovecot.org/releases/2.2/dovecot-2.2.17.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.17.tar.gz.sig A few director improvements since RC2, some fixes and a new plugin: http://wiki2.dovecot.org/Plugins/QuotaClone * Dovecot no longer checks or warns if a mountpoint is removed. This was causing more trouble than it was worth. Make sure that all the mountpoints that Dovecot

On 13 May 2015, at 01:15, Santiago Vila <sanvila at unex.es> wrote: > > On Wed, May 13, 2015 at 12:25:44AM +0300, Timo Sirainen wrote: >> - mbox: Fixed crash/corruption in some situations when the first mail >> was expunged. > > Once again: This is *not* fixed! One bug was fixed, but looks like there was another one. I tried after the fix that your test case

http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz.sig Quite a lot of changes, so here's a release candidate first. If no problems are reported I'll make v2.2.17 release early next week. Please test especially non-Linux systems as there are some larger configure/Makefile changes done since v2.2.16. * Dovecot no

http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.17.rc1.tar.gz.sig Quite a lot of changes, so here's a release candidate first. If no problems are reported I'll make v2.2.17 release early next week. Please test especially non-Linux systems as there are some larger configure/Makefile changes done since v2.2.16. * Dovecot no

On Wed, May 13, 2015 at 12:25:44AM +0300, Timo Sirainen wrote: > - mbox: Fixed crash/corruption in some situations when the first mail > was expunged. Once again: This is *not* fixed! I've just tested it on 2:2.2.17~rc1-1~auto+17 by Stephan Bosch, which is based on revision 18656:6f167f2e550d, and none of the changesets between 18656 and 18660 are related to this. Please try a

I'm now seeing these crashes in the indexing code: May 10 12:22:32 tornado.reub.net dovecot: master: Dovecot v2.2.17.rc1 (3903badc4ee0+) starting up for imap, lmtp, sieve ... May 10 13:07:50 tornado.reub.net dovecot: indexer: Error: Indexer worker disconnected, discarding 1 requests for reuben May 10 13:07:50 tornado.reub.net dovecot: indexer-worker(reuben): Fatal: master:

> Michael Grimm <trashcan at odo.in-berlin.de> kirjoitti 9.5.2015 kello 23.17: > > Hi ? > > Timo Sirainen <tss at iki.fi> wrote: > >> Please test especially non-Linux systems as there are some larger configure/Makefile changes done since v2.2.16. > > 2.2.17.rc1 will compile on FBSD 10.1 only, if bash has been installed Dovecot hg requires bash

On May 9, 2015, at 19:13 , Jerry <jerry at seibercom.net> wrote: >> 2.2.17.rc1 will compile on FBSD 10.1 only, if bash has been installed (see >> <554773D2.9060609 at dovecot.fi> from Teemu Huovila).[...]. But, maybe it's worth >> solving this issue for those non-linux systems without bash installed per >> default before releasing dovecot v2.2.17, finally.

On Sat, 9 May 2015 22:17:27 +0200, Michael Grimm stated: >Hi ? > >Timo Sirainen <tss at iki.fi> wrote: > >> Please test especially non-Linux systems as there are some larger >> configure/Makefile changes done since v2.2.16. > >2.2.17.rc1 will compile on FBSD 10.1 only, if bash has been installed (see ><554773D2.9060609 at dovecot.fi> from Teemu

Hi ? Timo Sirainen <tss at iki.fi> wrote: > Please test especially non-Linux systems as there are some larger configure/Makefile changes done since v2.2.16. 2.2.17.rc1 will compile on FBSD 10.1 only, if bash has been installed (see <554773D2.9060609 at dovecot.fi> from Teemu Huovila). This is from my point of view regarding portability issues "suboptimal". Both,

An easy way to start troubleshooting these is to look at the audit logs and see what SELInux is blocking. You have /McFrazier in the email.. if that's off the root tree than unless you've set permissions to allow httpd to look at tat folder, I bet that's one problem. if you run ls -Z you can see the labels that are present on those folders, that might be helpful too. On Wed, Mar 4,

Hey all, There's a website I help run that uses the Cassandra DB as its database. I notice that if I run the web server in SELinux permissive mode, the site works fine. But if I put it into enforcing mode, the site goes down with this error: Warning: require_once(/McFrazier/PhpBinaryCql/CqlClient.php): failed to open stream: Permission denied in

Hi Jeremy, An easy way to start troubleshooting these is to look at the audit logs and > see what SELInux is blocking. You have /McFrazier in the email.. if that's > off the root tree than unless you've set permissions to allow httpd to look > at tat folder, I bet that's one problem. > if you run ls -Z you can see the labels that are present on those folders, > that

Is there any support for NoSQL databases such as Cassandra (CQL) or MongoDB now or planned in the future for userdb and passdb lookups?

Hi, I'm using libexec/dovecot/imap via a ssh tunnel. 2.2.17 segfaults while accessing a NULL pointer. The following change fixes it for me: --- dovecot-2.2.17/src/lib-imap/imap-keepalive.c 2015-05-03 11:12:11.000000000 +0200 +++ dovecot-2.2.17/src/lib-imap/imap-keepalive.c 2015-05-14 20:06:29.490617405 +0200 @@ -11,6 +11,8 @@ { unsigned int addr; + if (!ip) + return FALSE; if

Hello dovecot community, first of all: dovecot ist great! ;) ...nevertheless I?ve got some problems to get my director scenario running as needed/expected :( My scenario: I?d like to configure two dovecot backends, without the need for multiple dovecot instances. Both backend servers are active/active and act on top of a glusterfs storage, which implies the need for dovecot director. As

On 10 May 2015, at 11:47, Reuben Farrelly <reuben-dovecot at reub.net> wrote: > Ok we have some (well, lots actually) of coredumps now: > > Program terminated with signal SIGSEGV, Segmentation fault. > #0 0x00007f4834fcc222 in fts_user_get_data_lang (user=0x16c7900) > at fts-user.c:302 Thanks, this should fix it: http://hg.dovecot.org/dovecot-2.2/rev/fddd3dbdf987

On 5/11/2015 9:26 AM, Dominik Breu wrote: > Hello, > > did an test Install on my system get some nice SEGFAULT > wich backtrace here: https://dominikbreu.de/Stikked/view/8b6b7e5b > version is following: > aptitude versions dovecot-sieve i 2:2.2.17~rc1-1~auto+4 I cannot view that URL (some broken SSL error). You can just put the backtrace in the email itself. Regards,

On 10/05/2015 5:47 PM, Timo Sirainen wrote: >> How do I go about debugging this further? How do I go about >> getting a backtrace on what is essentially a child process that >> doesn't produce a core? (Note that my installation normally does >> produce cores when it crashes, so there's something different about >> these indexer processes..) > > One