similar to: v2.2.33 released

https://dovecot.org/releases/2.2/rc/dovecot-2.2.33.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.33.rc1.tar.gz.sig There are a couple more small changes still coming, but this should be very close to the final release. I'm especially interested in hearing if there are any problems with doveadm log proxying or with director. We've improved our automated director tests quite a

https://dovecot.org/releases/2.2/rc/dovecot-2.2.33.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.33.rc1.tar.gz.sig There are a couple more small changes still coming, but this should be very close to the final release. I'm especially interested in hearing if there are any problems with doveadm log proxying or with director. We've improved our automated director tests quite a

try with 2.2.33.1 ---Aki TuomiDovecot oy -------- Original message --------From: Odhiambo Washington <odhiambo at gmail.com> Date: 13/10/2017 10:42 (GMT+02:00) To: Dovecot Mailing List <dovecot at dovecot.org> Cc: dovecot-news at dovecot.org Subject: Re: v2.2.33 released On 10 October 2017 at 18:28, Timo Sirainen <tss at iki.fi> wrote: >

I have just made an attempt at compiling 2.2.33.1 and it fails on one of my servers - FreeBSD 8.4 where 2.2.32 has been running happily: This is where I am going to start the tests before I move to the other servers (FreeBSD 9.3, 10.3, 11): mv -f .deps/maildir-settings.Tpo .deps/maildir-settings.Plo /bin/bash ../../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../..

https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz.sig Two more fixes since rc2. And repeating: There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are

https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz.sig Two more fixes since rc2. And repeating: There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are

> On 9 Sep 2018, at 18.42, Andreas Thienemann <andreas at bawue.net> wrote: > > Hi, > > I am attempting to migrate a mailspool from a cyrus server to a dovecot server using the dsync backup approach as described in the wiki at <https://wiki.dovecot.org/Migration/Dsync>. > > The first attempt works great. Everything copies over and a quick glance over the spool

https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz.sig There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level

https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.32.rc1.tar.gz.sig There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level

This lays 90% of the groundwork needed on the server side to support the use of a remote ipa server. Leaving the option disabled in the installer until the necessary node integration(dns/keytab placementi location) is completed Also apply: [PATCH server] update ovirt-add-host to use ipa commands instead of kadmin.local [PATCH server] separate ipa common tasks freeipa::common and rename

https://dovecot.org/releases/2.2/dovecot-2.2.33.2.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.33.2.tar.gz.sig One more patch release with some fixes: - doveadm: Fix crash in proxying (or dsync replication) if remote is running older than v2.2.33 - auth: Fix memory leak in %{ldap_dn} - dict-sql: Fix data types to work correctly with Cassandra

https://dovecot.org/releases/2.2/dovecot-2.2.33.2.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.33.2.tar.gz.sig One more patch release with some fixes: - doveadm: Fix crash in proxying (or dsync replication) if remote is running older than v2.2.33 - auth: Fix memory leak in %{ldap_dn} - dict-sql: Fix data types to work correctly with Cassandra

Hello Dovecot users, Here is the Pigeonhole hole release candidate that goes with the Dovecot release candidate. Nothing really special going on, just a few changes and fixes that accumulated over the last few months. Changelog v0.4.21: * redirect action: Always set the X-Sieve-Redirected-From header to sieve_user_email if configured. Before, it would use the envelope recipient instead if

Hello Dovecot users, Here is the Pigeonhole hole release candidate that goes with the Dovecot release candidate. Nothing really special going on, just a few changes and fixes that accumulated over the last few months. Changelog v0.4.21: * redirect action: Always set the X-Sieve-Redirected-From header to sieve_user_email if configured. Before, it would use the envelope recipient instead if

On 27 Mar 2019, at 1.25, Jason Lewis via dovecot <dovecot at dovecot.org> wrote: > > Hi Aki, > > debian jessie backports has been moved to archive.debian.org and > initially I was unable to install dovecot-dbg because of that. But I've > managed to resolve that issue now. > > This was the command I ran: > doveadm -D -f flow fetch imap.envelope mailbox

Thanks Timo. Given the age of these dovecot packages, and this being on debian oldstable, what should we do next? I'm inclined to just delete the email in question and move on. Jason Timo Sirainen wrote on 28/3/19 12:16 am: > On 27 Mar 2019, at 1.25, Jason Lewis via dovecot <dovecot at dovecot.org> wrote: >> >> Hi Aki, >> >> debian jessie backports has been

Hi, According to https://wiki2.dovecot.org/Variables you could use conditionals to assign values to a varible. The syntax is: %{if;value1;operator;value2;value-if-true;value-if-false} where any of the fields can refer to another field using %v or %{value} syntax. The problem is that when I use a config like: user_attrs = ...,=relpath=%{if;%u;eq;somevalue;valuetrue;valuefalse} it works

> On 10 Sep 2018, at 0.05, Andreas Thienemann <andreas at thienemann.net> wrote: > > Following the robustness principle it feels to me that it would make sense for dsync to disregard a duplicate header from a remote server and only use the first occurence. > > Would that be a good approach to the problem? Now that I understand the problem I am having, I can just workaround

This is a first go at adding support for the modern (based on the 1.0 virtio spec) virtio-pci implementation. kvmtool makes it simple to add additional transports such as this because of it's layering, so we are able to add it as a 3rd (after legacy virtio-pci and virtio-mmio) transport layer, and still allow users to choose to use either the legacy or the modern implementations (but setting

This is a first go at adding support for the modern (based on the 1.0 virtio spec) virtio-pci implementation. kvmtool makes it simple to add additional transports such as this because of it's layering, so we are able to add it as a 3rd (after legacy virtio-pci and virtio-mmio) transport layer, and still allow users to choose to use either the legacy or the modern implementations (but setting