similar to: Fwd: Dsync mail migration from v2.2 --> v2.3

Hello all, I?ve been battling how to migrate my imap mail following a new server install that has Dovecot and Postfix upgrades. The research seems pretty clear that the preferred method is to use dsync to get the mail from Server-A to B. After several hours and several different combos, I think I might finally have this working. However, before committing to my procedure and running it against

So, I'm still planning on getting v2.2.0 out Really Soon now. Unfortunately I've had to quickly develop some rather large features still at this stage. I was initially planning on leaving them for v2.3, but they were a requirement for one project and implementing them now to v2.2 was the least amount of trouble for me. (And yes, I'm aware I haven't replied to a lot of emails in

The git master branch starts tracking Dovecot v2.3 development from now on. There are soon going to be several API changes there that might break plugins. If you wish to keep tracking latest v2.2.x development instead, switch to master-2.2 branch. The nightly releases at http://dovecot.org/nightly/ will also track v2.3 tree.

The git master branch starts tracking Dovecot v2.3 development from now on. There are soon going to be several API changes there that might break plugins. If you wish to keep tracking latest v2.2.x development instead, switch to master-2.2 branch. The nightly releases at http://dovecot.org/nightly/ will also track v2.3 tree.

Hi Jan, fair enough. You may want to try mine to see if it works - if yes, it might be worthwhile digging deeper. Tbh I had not default settings on for a long time. Thanks and regards Goetz R. Schultz On 06/01/18 18:30, Jan Vejvalka wrote: > Thanks for your reply; I used the defaults, both before and after the > upgrade, cf. https://wiki2.dovecot.org/Upgrading/2.3 -> Setting

Hi *, The change in default SSL settings between 2.2 and 2.3 cut off a few clients; Microsoft-hosted Exchange (?) being one of them: Jan 4 11:02:56 kremail dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=40.101.4.hisip, lip=myip, TLS handshaking: SSL_accept() failed: error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher,

Jan Vejvalka <jan.vejvalka at lfmotol.cuni.cz> writes: >> Mine are below and they work just fine: >> >> ssl_cipher_list = >>

Thanks for your reply; I used the defaults, both before and after the upgrade, cf. https://wiki2.dovecot.org/Upgrading/2.3 -> Setting default changes. The new defaults broke the connection. Jan > what are your settings? > > Mine are below and they work just fine: > > ssl_cipher_list = >

# === The post relates to Dovecot v2.2 running on AWS Linux v1 === # Hello all? The Dovecot sockets on this server are installed in two different locations one of which is different from what I have on my other Dovecot installations which run on Centos-7. Here are the sockets paths: ? all sockets EXCEPT "auth-master? ?> "/usr/local/var/run/dovecot? <<<<< this

http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz.sig I wanted to start stabilizing v2.2 release some months ago already, but I somehow got stuck adding more and more features. Now it looks like all of the necessary API changes are done, so everything I'm planning on near future can still be added to v2.2 without

http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz.sig I wanted to start stabilizing v2.2 release some months ago already, but I somehow got stuck adding more and more features. Now it looks like all of the necessary API changes are done, so everything I'm planning on near future can still be added to v2.2 without

Hi, Now that we have a new Dovecot v2.3 release, I've created a new Xi builder that follows the git master branch to automatically produce Debian packages for the future Dovecot v2.4. The existing v2.3 repository now follows the master-2.3 branch, meaning that this will only follow developments/fixes ported to the v2.3 stable release series. This was already true for the v2.2 oldstable

Dear all, A couple of months ago, it has been mentioned that multiple users experienced a problem regarding the synchronisation of Sieve scripts by means of "dsync" (whereas e-mails were replicated just fine between servers) [1][2] for Dovecot v2.3.x; the same problem apparently occurred with early versions from the v2.2 branch some three years ago but has been marked/confirmed as

http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz.sig Lots of fixes since 2.2.alpha1, especially related to dsync. Also dsync now supports syncing private message flags when INDEXPVT is used. Here's again the list of all the major changes in v2.2: * When creating home directories, the permissions are copied from the

http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz.sig Lots of fixes since 2.2.alpha1, especially related to dsync. Also dsync now supports syncing private message flags when INDEXPVT is used. Here's again the list of all the major changes in v2.2: * When creating home directories, the permissions are copied from the

http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig This could be (one of) the last v2.2.x release. We're starting v2.3 development soon. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login:

http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig This could be (one of) the last v2.2.x release. We're starting v2.3 development soon. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login:

http://dovecot.org/releases/2.2/dovecot-2.2.0.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.0.tar.gz.sig Everything now seems to be stable and working in v2.2, so I can finally move onto developing great new interesting features for v2.3. :) My company has also launched a web shop where you can buy various products. One of them is cheap access to Dovecot enterprise edition repositories,

http://dovecot.org/releases/2.2/dovecot-2.2.0.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.0.tar.gz.sig Everything now seems to be stable and working in v2.2, so I can finally move onto developing great new interesting features for v2.3. :) My company has also launched a web shop where you can buy various products. One of them is cheap access to Dovecot enterprise edition repositories,

http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta2.tar.gz.sig A ton of fixes since beta1. Especially the new dsync and the replication server related to that should really work now. It also works correctly now for shared mailboxes with private \Seen flags. And the replication server uses incremental syncing after the initial full