similar to: v2.2.28 release candidate 2 released

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 * director: "doveadm director move" to same host now refreshes user's timeout. This allows keeping user constantly in the same backend by just periodically moving the user there. * When new mailbox is created, use initially INBOX's dovecot.index.cache

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 * director: "doveadm director move" to same host now refreshes user's timeout. This allows keeping user constantly in the same backend by just periodically moving the user there. * When new mailbox is created, use initially INBOX's dovecot.index.cache

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 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

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 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 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

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 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...

Compiled on CentOS 6 and CentOS 7 successfully. On 10/19/2016 3:01 PM, Timo Sirainen wrote: > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig > > There are quite a lot of changes since v2.2.25. Please try out this RC so we can get a good and stable v2.2.26 out. > > * master: Removed hardcoded 511

Hi, Do you plan on inclinding the following patch in the final release? http://www.dovecot.org/list/dovecot/2016-October/105734.html I have some tests in place and can backport the patch if necessary. Regards, On 10/19/2016 11:01 PM, Timo Sirainen wrote: > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig

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

Timo Sirainen wrote on 20.10.2016 04:01: > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig > > There are quite a lot of changes since v2.2.25. Please try out this RC so we can get a good and stable v2.2.26 out. > > * master: Removed hardcoded 511 backlog limit for listen(). The kernel > should

Hi experts. in the output of imapsync I found: Host2: found quota, presented in raw IMAP Sending: 7 GETQUOTAROOT INBOX Sent 22 bytes Read: * QUOTAROOT INBOX "User quota" * QUOTA "User quota" (STORAGE 420325 1953125) 7 OK Getquotaroot completed (0.001 + 0.000 secs). Host2: Quota current storage is 430412800 bytes. Limit is 2000000000 bytes. So

On 10/20/2016 10:34 PM, Aki Tuomi wrote: >> On October 21, 2016 at 6:27 AM Tamsy <dovecot-list at mohtex.net> wrote: >> >> >> Timo Sirainen wrote on 20.10.2016 04:01: >>> http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz >>> http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig >>> >>> There are quite a lot of

This is a followup to my thread "Recommended Protocols?". The error message is as follows: dovecot: imap-login: Disconnected: TLS: SSL_read() failed: SSL routines:ssl3_read_bytes:sslv3 alert bad certificate: SSL alert number 42 I have selected both SSL/TLS and STARTTLS on the Thunderbird side, with identical results. The first question that I have is this. Is there any way to know

Hi, I've a broken IMAP server, which doesn't support pipelining and fails on dovecot's attempt to do this ([C] is dovecot's imapc, [S] is the IMAP server): [C] 24 LOGIN "user" "pass" [S] 23 OK [C] 25 SELECT "INBOX" [C] 23 UID FETCH 2 (INTERNALDATE) [S] 25 OK [S] 23 BAD No mailbox selected Sadly, fixing the server would be a hard task, turning off