similar to: v2.2.28 released

http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc2.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc2.tar.gz.sig I'm assuming that most of the bugs are now found and fixed, so the final 2.2.28 should be out in a day or two. Changes since rc1: * Reverted [UNKNOWN-CTE] -> [PARSE] change + pop3c: Added pop3c_features=no-pipelining setting to prevent using PIPELINING extension

http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc2.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc2.tar.gz.sig I'm assuming that most of the bugs are now found and fixed, so the final 2.2.28 should be out in a day or two. Changes since rc1: * Reverted [UNKNOWN-CTE] -> [PARSE] change + pop3c: Added pop3c_features=no-pipelining setting to prevent using PIPELINING extension

http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc1.tar.gz.sig Pretty large release. Please test before the final v2.2.28, which should be out in a few days. BTW. Our plan is to start making new releases approximately every month from now on. * director: "doveadm director move" to same host now refreshes user's

http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc1.tar.gz.sig Pretty large release. Please test before the final v2.2.28, which should be out in a few days. BTW. Our plan is to start making new releases approximately every month from now on. * director: "doveadm director move" to same host now refreshes user's

On 07.03.2017 10:52, Nagy, Attila wrote: > On 03/06/2017 11:30 PM, Timo Sirainen wrote: >> On 6 Mar 2017, at 9.17, Tom Sommer <mail at tomsommer.dk> wrote: >>> >>> On 2017-02-24 14:34, Timo Sirainen wrote: >>>> http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz >>>> http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig >>>

On 6 Mar 2017, at 9.17, Tom Sommer <mail at tomsommer.dk> wrote: > > > On 2017-02-24 14:34, Timo Sirainen wrote: >> http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz >> http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig > > Are there any plans to do a bugfix-release, that includes the few issues seen in the mailing-list, or do you consider 2.2.28 safe

On 2017-02-24 14:34, Timo Sirainen wrote: > http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz > http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig Are there any plans to do a bugfix-release, that includes the few issues seen in the mailing-list, or do you consider 2.2.28 safe to upgrade to? Thanks --- Tom

On 03/06/2017 11:30 PM, Timo Sirainen wrote: > On 6 Mar 2017, at 9.17, Tom Sommer <mail at tomsommer.dk> wrote: >> >> On 2017-02-24 14:34, Timo Sirainen wrote: >>> http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz >>> http://dovecot.org/releases/2.2/dovecot-2.2.28.tar.gz.sig >> Are there any plans to do a bugfix-release, that includes the few issues

On 20 February 2017 at 13:15, Timo Sirainen <tss at iki.fi> wrote: > http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc1.tar.gz > http://dovecot.org/releases/2.2/rc/dovecot-2.2.28.rc1.tar.gz.sig > > Pretty large release. Please test before the final v2.2.28, which should > be out in a few days. > > BTW. Our plan is to start making new releases approximately every

I upgraded to 2.2.28 and started seeing this logged: indexer-worker(dluke): Panic: file mailbox-list.c: line 1158 (mailbox_list_try_mkdir_root): assertion failed: (strncmp(root_dir, path, strlen(root_dir)) == 0) indexer-worker(dluke): Error: Raw backtrace: 2 libdovecot.0.dylib 0x000000010ec63d24 default_fatal_finish + 36 -> 3 libdovecot.0.dylib

Hi, I'm using autoexpunge to clean my users' Trash and Spam mailboxes. But I'm also using lazy_expunge to keep a copy of deleted messages. Is there any to configure lazy_expunge namespace to be autoexpunged too? My lazy_expunge configuration is the "1 Namespace" described at https://wiki2.dovecot.org/Plugins/Lazyexpunge -- Angel L. Mateo Mart?nez Secci?n de

On Mon Feb 20 2017 05:15:34 GMT-0500 (Eastern Standard Time), Timo Sirainen <tss at iki.fi> wrote: > + auth: Support OAUTHBEARER and XOAUTH2 mechanisms. Also support them > in lib-dsasl for client side. So... does this mean dovecot now has OAUTH2 support? If so... yay! and I'll go open a Thunderbird bug to add support for dovecot's OAUTH2...

Hi, I am investigating the use of dovecot for a voicemail storage system (which is effectively a SMTP/POP3 system), which we want to use replication to give us some resilience. Tests have mostly been on dovecot 2.3.8 (9df20d2db) - as packaged on Centos 8 - but I have also used a couple of similar versions on different platforms, so this is not a specific build problem. The platform has

Timo, re: What OS is this? OS 10.12.3 with Xcode 8.2.1 and the official clang 3.9.0 re: test-time-util.c t_strftime and variants now .......................................... : ok Info: 'Thu, 08 Dec 2016 18:42:16 +0100' test-time-util.c:124: Assert failed: strcmp(t_strftime(RFC2822_FMT, gmtime(&ts)), exp) == 0 Info: 'Thu, 08 Dec 2016 18:42:16 +0100'

Hello Dovecot users, Here's the definitive 0.4.17 release. There were no changes since the release candidate. Changelog v0.4.17: - LDA Sieve plugin: Fixed handling of an early explicit keep during multiscript execution. Action side-effects and the message snapshot would be lost at the final stage where the implicit keep is evaluated. This could result in the IMAP flags assigned to the

Hi, On 20-Feb-17 12:15, Timo Sirainen wrote: > imap: When BINARY FETCH sees invalid content, return NO [PARSE] reply > instead of [UNKNOWNCTE] (which is now used only for actually unknown > Content-Transfer-Encoding headers). Has this been tested with Roundcube webmail? I know Roundcube has some workarounds when dovecot now responds with that "[UNKNOWNCTE]". Best

On 20.02.2017 12:47, Toni Mattila wrote: >> imap: When BINARY FETCH sees invalid content, return NO [PARSE] reply >> instead of [UNKNOWNCTE] (which is now used only for actually unknown >> Content-Transfer-Encoding headers). > > Has this been tested with Roundcube webmail? I know Roundcube has some > workarounds when dovecot now responds with that

> On Feb 20, 2017, at 5:18 PM, Stephan Bosch <stephan at rename-it.nl> wrote: > > Changelog v0.4.17: > I didn?t see this reported bug listed in the changelog, did it get fixed? >> >> On January 12, 2017 at 9:55 PM Matt Simpson <dclist at list.jmatt.net> wrote: >> >> >> I?m running dovecot 2.2.27 and pigeonhole 0.4.16 on FreeBSD 11.

On 25 Feb 2017, at 21.11, Ruga <ruga at protonmail.com> wrote: > > t_strftime and variants now .......................................... : ok > > > test-time-util.c:123: Assert failed: strcmp(t_strftime(RFC2822_FMT, gmtime(&ts)), exp) == 0 > > > test-time-util.c:124: Assert failed: strcmp(t_strfgmtime(RFC2822_FMT, ts), exp) == 0 > > > t_strftime

On 25 Feb 2017, at 21.54, Timo Sirainen <tss at iki.fi> wrote: > > Oh, I forgot to remove the #if OPENSSL_VERSION_NUMBER checks from lib-dcrypt. Will be removed in v2.2.29. Attached the planned patch that should do it. Well that didn't work with <v1.1. Maybe this one. -------------- next part -------------- A non-text attachment was scrubbed... Name: openssl.diff Type: