similar to: METADATA / ANNOTATE extensions

Hi Timo, congrats to the merger with OX. Currently the implementation of RFC 5257, ANNOTATE-EXPERIMENT-1, has only low priority on http://wiki2.dovecot.org/Roadmap I want to explain a scenario that would benefit from annotation support to - maybe - increase the priority in your roadmap: I'm currently working on a project to publish bank customer related documents inside a banking

On 21 Mar 2015, at 10:14, Florian Sager <sager at agitos.de> wrote: > > Hi Timo, > > congrats to the merger with OX. > > Currently the implementation of RFC 5257, ANNOTATE-EXPERIMENT-1, has > only low priority on http://wiki2.dovecot.org/Roadmap > I want to explain a scenario that would benefit from annotation support > to - maybe - increase the priority in your

Hello, Does Dovecot support the IMAP ANNOTATE Extension RFC5257 http://tools.ietf.org/html/rfc5257? If not, are there any plans to implement the extension? If not, why there is no plan to implement this feature? Regards Sebastian

I have not seen mention of using dsync for clustering Dovecot in some time on the mailing list, but I believe Timo was going to write a wiki page when v2.2 became more mature. Does this documentation exist yet, or are there any resources on what dsync replication is capable of at this point (looking on the wiki and google didn't reveal much)? Thank in advance.

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/rc/dovecot-2.2.rc2.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc2.tar.gz.sig Looks like the last changes I did today just before rc1 release made it just about unusable. This one is actually running on my servers. :)

http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc2.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc2.tar.gz.sig Looks like the last changes I did today just before rc1 release made it just about unusable. This one is actually running on my servers. :)

Hello, I'm in the process of migrating mailbox from one dovecot server running dovecot 2.1.9 with mailboxes stored in maildir format to a newer one running 2.1.16 with mailboxes stored in mdbox format. To migrate mailboxes I'm using dsync as explained at http://wiki2.dovecot.org/Tools/Dsync. The command I'm running in the newer server is: sudo dsync -o mailbox_list_index=no

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

In https://wiki2.dovecot.org/Tools/Doveadm/Sync#section_arguments the destination list 5 possible options for the destination but in the page on migration https://wiki2.dovecot.org/Migration/Dsync it seems to use a sixth undocumented "imapc:" option for destination e.g. doveadm -o mail_fsync=never backup -R -u user at domain imapc: "imapc:" is also referenced on

Dear all i'm planning a transparent migration from a courier server that provides both IMAP and POP3 access to users to a remote dovecot server with both IMAP and POP3 access. I have to migrate about 2500 users for 250 GB of space. I'm using dovecot 2.2.5.4 on debian6 squeeze. To make a transparent migration i have to maintain old IMAP UIDs and POP3 UIDs, so i've read

I forked the wiki to http://wiki1.dovecot.org/ is the old docs for v1.x http://wiki2.dovecot.org/ is the new docs for v2.0 For now wiki.dovecot.org points to wiki1, but once v2.0 is released I'll change it to point to wiki2. I symlinked the user directory, so users should stay synced between the wikis. The main reason for wiki2 is to be able to describe Dovecot v2.0's actual behavior

Hello everbody, I'm a proud user of Dovecot 2.2.9 on Ubuntu 14.04 LTS. I currently migrate all my Linux services to a new Debian 8 Jessie Server. On this server I installed and configured Dovecot 2.2.24. Now I search a way to migrate the two IMAP users I have on this server preserving all timestamps, folders and flags. Yes, only two ;-) I read the following two articles:

On 27 Oct 2016, at 15:29, Tanstaafl <tanstaafl at libertytrek.org> wrote: > > On 10/26/2016 2:38 AM, Gandalf Corvotempesta > <gandalf.corvotempesta at gmail.com> wrote: >> This is much easier than dovecot replication as i can start immedialy with >> no need to upgrade the old server >> >> my only question is: how to manage the email received on the

Hello List, i have a simple and maybe stupid question but, read the guide on http://wiki2.dovecot.org/Migration/Dsync now i wonder where to put this configuration ? May i oversee something but i would appreciate any hint toward solving my problem. regards, dominik

Il 04/12/2017 14:33, x9p ha scritto: > >> Can I use this tool even if I do not know the other remote server >> typology? >> > sure. just need both IMAP ports reachable and valid user/pass for both > servers. I think Davide was asking about dsync. If so, the answer is no: dsync works only when both servers are Dovecot and needs some additional configuration to work