Displaying 20 results from an estimated 3000 matches similar to: "mbox "Next message unexpectedly lost" bug fixed"
2007 Mar 18
1
Login processes and a new performance/security compromise [was: Re: pre-1.0.rc27: Index and mbox fixes]
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
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:
2006 Dec 07
0
Rmpi help
Hi team,
I am beginning on R and I try to install Rmpi library and I have problems, I have installed LAM-MPI on Rocks;
[rcnavarro at hpc-cip ~]$ laminfo
LAM/MPI: 7.1.1
Prefix: /opt/lam/gnu
Architecture: x86_64-unknown-linux-gnu
Configured by: root
Configured on: Wed Oct 19 18:12:25 EDT 2005
Configure host: rocks-156.sdsc.edu
Memory
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 Jul 19
6
v1.1.alpha1 released
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
2007 Jul 19
6
v1.1.alpha1 released
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
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
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 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 Nov 17
0
ManageSieve SECURITY hole: virtual users can edit scripts of other virtual users (all versions)
Hello,
While updating the ManageSieve implementation to the latest draft
specification I noticed a major omission in the way script names are
handled. Essentially, script names are directly appended to the sieve
storage directory path and suffixed with '.sieve'. This does not take
the use of '../' in script names into account. Therefore, clever virtual
users that know the
2008 Nov 17
0
ManageSieve SECURITY hole: virtual users can edit scripts of other virtual users (all versions)
Hello,
While updating the ManageSieve implementation to the latest draft
specification I noticed a major omission in the way script names are
handled. Essentially, script names are directly appended to the sieve
storage directory path and suffixed with '.sieve'. This does not take
the use of '../' in script names into account. Therefore, clever virtual
users that know the
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
2012 Jun 28
1
Merging listed dataset into one
Hello,
I'm wondering how I can merge two featuresets into one.
My dataset is two sets of microarray data and it looks like followings:
> rawData
$v1
TilingFeatureSet (storageMode: lockedEnvironment)
assayData: 2197815 features, 59 samples
element names: channel1, channel2
protocolData
rowNames: LT290677RU_D1_2011-02-16 LT286300LU_D1_2010-07-24 ...
LT003990RU_D1_2010-11-04 (59
2007 Dec 03
0
De-duplication / Single Instance Storage - WAS: Re: Updated v1.1 and summer plans
On 12/2/2007, Timo Sirainen (tss at iki.fi) wrote:
> On Sun, 2007-12-02 at 10:02 -0500, Charles Marcus wrote:
>> Do you have any idea as to a time frame for when you might be able
>> to get to it (Single instance Storage)? Are you thinking post
>> v2.0? Even 2.1 or 3.0?
> Right now I just want to get v1.1 finished. The main problem with it
> is that apparently in
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
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,
2013 Jan 13
0
[LLVMdev] Using C++'11 language features in LLVM itself
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