similar to: De-duplication / Single Instance Storage - WAS: Re: Updated v1.1 and summer plans

Displaying 20 results from an estimated 10000 matches similar to: "De-duplication / Single Instance Storage - WAS: Re: Updated v1.1 and summer plans"

2007 May 21
3
Updated v1.1 and summer plans
Webmail.us will be sponsoring my Dovecot development for this summer. Other companies are also welcome to participate in the costs. Participation gets you: - listed in Credits in www.dovecot.org - listed in AUTHORS file - you can tell me how you want to use the feature and I'll make sure that it supports it (within reasonable limits) For already implemented v1.1 features, see
2007 Dec 01
2
Updated v1.1 and summer plans
Timo Sirainen, on 5/21/2007 8:54 AM, said the following: <snip> > Upcoming v1.1 features, more or less implemented in this order: <snip> Hey Timo, I'm loving all of the new functionality - especially the full support for Shared mailboxes and ACLs... but... I don't see any mention of support for SiS (single-instance-storage) as discussed previously on the list, even for
2007 Apr 17
14
v1.1 plans
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
2007 Jun 30
3
v1.1 max connections per user
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!
2009 Dec 17
5
Dovecot v2.0 wiki
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
2010 Aug 26
3
Single instance storage - testing please
http://hg.dovecot.org/dovecot-2.0-sis contains the code for it. Otherwise it's the latest (as of writing this) dovecot-2.0 hg tree. Please test if you're interested in SIS. :) Once there's at least some testing, I'll probably add this to v2.0.x since very little of this new code is used when SIS is disabled (which is the default of course). SIS works pretty much like explained in
2007 Jul 12
3
v1.1 status and benchmarks
v1.1 plans have changed a bit. I'll release v1.1.alpha1 soon and hope to have a stable v1.1 in a month or two. The rest of the features that didn't make it into v1.1 will go to v1.2. I'll write more about this when v1.1 alpha is released. I also did a bit of benchmarking. v1.1's performance improvements are looking pretty great, it seems to be twice as fast as v1.0. v1.0:
2018 Mar 31
0
Migrate from Tinc-VPN v1.0 to TINC-VPN v1.1
El 31 de marzo de 2018 17:58:18 CEST, Rafael Wolf <rfwolf at gmail.com> escribió: >Can you just compile the latest from the git repo on to raspian os? > > > >On Sat, Mar 31, 2018, 11:21 AM Ramses <ramses.sevilla at gmail.com> wrote: > >> El 29 de marzo de 2018 23:41:24 CEST, Ramses ><ramses.sevilla at gmail.com> >> escribió: >> >Hi
2007 Apr 17
1
v1.1 plans - sieve?
In the 1.1 plans (http://dovecot.org/list/dovecot/2007-April/021974.html) I don't see any mention of sieve... is this intentional? Sieve support is a priority for me... I'm going to have to see if I can get it via exim's support if dovecot's not going to add it in 1.1. Cheers, David
2007 Aug 07
1
v1.1.alpha2 released
http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha2.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha2.tar.gz.sig Hopefully the next release can be v1.1.beta1. I'm not aware of any major problems and I think I'm pretty much done with new features (except for dbox). The largest changes since alpha1: * Removed THREAD indexing. It's a bit buggy and I think
2007 Dec 09
1
v1.1.beta11 released (Problems)
On Dec 9, 2007, at 1:48 PM, dovecot-request at dovecot.org wrote: > > > Message: 7 > Date: Sun, 09 Dec 2007 20:29:49 +0200 > From: Timo Sirainen <tss at iki.fi> > Subject: [Dovecot] v1.1.beta11 released > To: dovecot at dovecot.org > Message-ID: <1197224989.922.405.camel at hurina> > Content-Type: text/plain; charset="us-ascii" > >
2008 Feb 16
0
v1.1.beta16 released
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta16.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta16.tar.gz.sig If all goes well, I'll release v1.1.rc1 in a couple of days. Now's a good time to start testing v1.1 :) Changes since beta15: - Squat is finally working and supports expunging messages from it. I've been stress testing it and can't find any problems
2018 Mar 31
0
Migrate from Tinc-VPN v1.0 to TINC-VPN v1.1
El 29 de marzo de 2018 23:41:24 CEST, Ramses <ramses.sevilla at gmail.com> escribió: >Hi everyone, > >I have installed Tinc-VPN v1.0.19-3, that is the last version that >there is in Raspbian 7, installed with the apt-get command. > >I will like know what will be the best way to migrate this version to >Tinc-VPN v1.1 > > >Regards, > >Ramses Hi everyone,
2018 Apr 01
0
Migrate from Tinc-VPN v1.0 to TINC-VPN v1.1
El 1 de abril de 2018 3:34:46 CEST, Lars Kruse <lists at sumpfralle.de> escribió: >Hello Ramses, > > >Am Sun, 01 Apr 2018 01:44:01 +0200 >schrieb Ramses <ramses.sevilla at gmail.com>: > >> [..] >> >> Correct? > >in general, this is exactly the right procedure. > > >> I have installed Raspbian 7 (Wheezy). I will have problems doing
2008 May 30
4
v1.1.rc6 released
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz.sig This is it. The first v1.1 release that actually deserves the "release candidate" name. It contains everything I require from v1.1.0 release. There are two bugs left that I'd like to get fixed, but they won't block v1.1.0 release: *
2008 May 30
4
v1.1.rc6 released
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz.sig This is it. The first v1.1 release that actually deserves the "release candidate" name. It contains everything I require from v1.1.0 release. There are two bugs left that I'd like to get fixed, but they won't block v1.1.0 release: *
2007 Dec 22
0
v1.1.beta12 deliver crashes (arvids) Ditto!
On Dec 22, 2007, at 5:00 AM, dovecot-request at dovecot.org wrote: (stuff cut out) > Message: 10 > Date: Sat, 22 Dec 2007 11:12:30 +0200 > From: arvids <arvids at mpe.lv> > Subject: [Dovecot] v1.1.beta12 deliver crashes > To: Dovecot Mailing List <dovecot at dovecot.org> > Message-ID: <200712221112.30760.arvids at mpe.lv> > Content-Type: text/plain;
2018 Mar 31
2
Migrate from Tinc-VPN v1.0 to TINC-VPN v1.1
Can you just compile the latest from the git repo on to raspian os? On Sat, Mar 31, 2018, 11:21 AM Ramses <ramses.sevilla at gmail.com> wrote: > El 29 de marzo de 2018 23:41:24 CEST, Ramses <ramses.sevilla at gmail.com> > escribió: > >Hi everyone, > > > >I have installed Tinc-VPN v1.0.19-3, that is the last version that > >there is in Raspbian 7,
2008 Feb 21
4
v1.1.rc1 released
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz.sig Finally the first v1.1 release candidate. Please test so we can have a fully stable v1.1.0 release. v1.1.betas are already running in a few large installations, so I don't expect there to be many bugs left. There are no release critical bugs left and no known crash bugs.
2008 Feb 21
4
v1.1.rc1 released
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz.sig Finally the first v1.1 release candidate. Please test so we can have a fully stable v1.1.0 release. v1.1.betas are already running in a few large installations, so I don't expect there to be many bugs left. There are no release critical bugs left and no known crash bugs.