similar to: upgrading from 1.0 to 1.1

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post. This is the only v1.1.alpha announcement I send

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post. This is the only v1.1.alpha announcement I send

On Sat, March 17, 2007 10:51 pm, Timo Sirainen <tss at iki.fi> said: > Oh, and as for when the rewrite is in CVS, I'm not really sure. I'm > still wondering if I should put it there soon and make the release after > v1.0 be v2.0, or if I should first stabilize the current new CVS HEAD > features (which shouldn't take too long), do a v1.2 release and only > then

On Sun, Jan 13, 2013 at 10:26 AM, Tim Northover <t.p.northover at gmail.com> wrote: >> Good points David, I don't feel qualified to evaluate the differences >> between those versions though... Perhaps Richard or Doug could comment here? > > Unless I'm misreading the buildbots, we don't actually have anything > trying to build with MSVC. Have we considered how

On Sun, Jan 13, 2013 at 7:39 PM, David Blaikie <dblaikie at gmail.com> wrote: > On Sun, Jan 13, 2013 at 10:26 AM, Tim Northover <t.p.northover at gmail.com> > wrote: > >> Good points David, I don't feel qualified to evaluate the differences > >> between those versions though... Perhaps Richard or Doug could comment > here? > > > > Unless

I have been trying to find information and possible issues with running a cluster of dovecot server with different versions without any luck. We have an existing cluster with dovecot v1.1.10 and tried migrating to a new cluster with dovecot v2.0.12. We ran into some issues when we moved traffic to the new cluster and have been unable to reproduce it in our own testing. We may need to put real

I think I won't do any actual releases until it's mostly feature complete. Then maybe v1.1.alpha1 or v1.1.beta1. So if you want to test it before then, use CVS or the nightly snapshots. I'm planning on keeping v1.1 almost completely compatible with v1.0. There could be some minor configuration file changes, but for most people v1.0's dovecot.conf should work with v1.1. I want to

Hi all, We have put together a firmware for a range of inexpensive routers. It has been configured to provide optimum VoIP performance. We have internally tested it for number of months and it looks very good. You should be able to run it easily with 20+ phones on local network ( we still did not hit the upper limit ) assuming that you have bandwidth. Your VoIP will get prioritized over other

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

In v1.0 .. v1.1 deliver was writing incoming >128k mail to /tmp file (to avoid reading it all into memory). In v1.2 I moved it to user's home directory. This slowed deliveries for NFS users. Also people with filesystem quota had trouble since now user required twice as much available quota to save a message. The FS quota problem was "solved" by having quota-fs plugin change the

It's long over due, but now I finally plan on upgrading from v1.0.15 to v1.2.16 on our servers. Would appreciate any comments! We have 7 servers, all running of the same GPFS filesystem. Both maildirs and indexes are stored here. We use dovecot for POP/IMAP and deliver. Currently we're using mysql as authentication source, but want to move to using ldap instead. Can we upgrade one server

v1.1 has now: # Maximum number of connections allowed for a user. The limits are enforced # separately for IMAP and POP3 connections, so you can move this setting # inside protocol {} to have separate settings for them. NOTE: The user names # are compared case-sensitively, so make sure your userdb returns usernames # always using the same casing so users can't bypass this limit!

Hi all We are planning to upgrade Dovecot from production version 1.0.10 to latest version 1.2.9 Users are using maildir style mailboxes with ~20 GB of messages on SLES10 server. Upgrade will be done by installing new server and then migrating mailboxes from old on new server. Since dovecot-uidlist file have new format and index files have changed in v1.1, what must be done to have new

On Sun, Jan 13, 2013 at 5:18 AM, Matthieu M. <matthieu.monrocq at gmail.com> wrote: > Hello all, > > Using the Apache Wiki [1] I summed up what can be used simultaneously by gcc, > MSVC and clang. > > I mostly considered only the latest versions of the proposals where there were > several, where not there is a link to a note at the bottom. Furthermore I did > not

http://dovecot.org/releases/dovecot-1.0.0.tar.gz http://dovecot.org/releases/dovecot-1.0.0.tar.gz.sig It took almost 5 years, but it's finally ready. I'm not expecting to release v1.0.1 anytime soon, unless someone's been sitting on a major bug just waiting for v1.0 to be released. :) People wanting new features should start testing the upcoming v1.1. http://dovecot.org/nightly/

http://dovecot.org/releases/dovecot-1.0.0.tar.gz http://dovecot.org/releases/dovecot-1.0.0.tar.gz.sig It took almost 5 years, but it's finally ready. I'm not expecting to release v1.0.1 anytime soon, unless someone's been sitting on a major bug just waiting for v1.0 to be released. :) People wanting new features should start testing the upcoming v1.1. http://dovecot.org/nightly/

Hi all, ok, I couldn't quite find this in any of the documentation, so I figured I would ask here. In preparation to move to version 2.0 to take advantage of the mutiple IP and SSL cert options that are coming, it would be really nice to be able to include other config files in the main config file, so that I don't have to edit the main config in order to add new IP addresses or certs...

On Sun, Jan 13, 2013 at 9:57 AM, David Blaikie <dblaikie at gmail.com> wrote: > On Sun, Jan 13, 2013 at 5:18 AM, Matthieu M. <matthieu.monrocq at gmail.com> wrote: >> Hello all, >> >> Using the Apache Wiki [1] I summed up what can be used simultaneously by gcc, >> MSVC and clang. >> >> I mostly considered only the latest versions of the proposals

v1.1.0 is finally getting closer, so it's time to start planning what happens after it. Below is a list of some of the larger features I'm planning on implementing. I'm not yet sure in which order, so I think it's time to ask again what features companies would be willing to pay for? Sponsoring Dovecot development gets you: - listed in Credits in www.dovecot.org - listed in

I am running Dovecot 1.2.16 and considering moving up to 2.0.8. I have found <http://wiki2.dovecot.org/Upgrading/2.0> but there's not a lot about deploying a 2.0 server alongside an existing 1.2. Any hints on a seamless approach to this, especially one that might allow me to upgrade individual users in place, without moving their maildirs into a new tree and still avoid issues with