Re: messages removed before expire

2014-10-16 Thread Stephen Ingram
On Thu, Oct 2, 2014 at 8:48 AM, Stephen Ingram wrote: > On Tue, Sep 16, 2014 at 11:15 PM, Bron Gondwana wrote: > >> On Wed, Sep 17, 2014, at 08:24 AM, Stephen Ingram wrote: >> >> On Tue, Sep 16, 2014 at 3:02 PM, Bron Gondwana wrote: >> >> >> Dumb question - but I don't suppose anything happene

Re: Upgrading from 2.2 to 2.4 (slow cyr_expire)

2014-10-16 Thread Andrew Morgan
On Thu, 16 Oct 2014, Jay Sekora wrote: > Hi. I recently tried to upgrade/migrate our Cyrus deployment from > 2.2.13 (on Debian) to 2.4.17 (on Ubuntu 14.04). In our environment, > user mailboxes (about 3TB of them) are on iSCSI volumes; everything else > is on local disk (which I rsync'ed). > > I

Upgrading from 2.2 to 2.4 (slow cyr_expire)

2014-10-16 Thread Jay Sekora
Hi. I recently tried to upgrade/migrate our Cyrus deployment from 2.2.13 (on Debian) to 2.4.17 (on Ubuntu 14.04). In our environment, user mailboxes (about 3TB of them) are on iSCSI volumes; everything else is on local disk (which I rsync'ed). I ran into some delays to do with the storage backen

Patch for adding tls_honor_cipher_order

2014-10-16 Thread Kristian Kræmmer Nielsen
Hi, Patch attached. While at it we might as well also let the user set tls_honor_cipher_order if they want to so that the order of cipher specified using tls_cipher_list is honored. By default false, so changes nothing. For expert uses might give clients a bit of extra performance by usin

Re: cyrus-imap patching POODLE and another for adding perfect forward secrecy (PFS)

2014-10-16 Thread Kristian Kræmmer Nielsen
Hi Geoff, I am basically not trying to take any stand on this. I just think it is time for the users to be able to disable the older protocols if they want to - as the old protocols are really no longer necessary for the wide majority of clients - and that is the main reasoning by my patche

Re: How to prevent SSLv3/Poodle attack?

2014-10-16 Thread Geoff Winkless
On 16 October 2014 11:14, Sven Schwedas wrote: > On 2014-10-15 18:20, Geoff Winkless wrote: > > Well the only thing new about POODLE versus previous known > > vulnerabilities is the way to manipulate the known vulnerability to gain > > the session cookie, which you can then re-use to log on to th

Re: How to prevent SSLv3/Poodle attack?

2014-10-16 Thread Sven Schwedas
On 2014-10-15 18:20, Geoff Winkless wrote: > Well the only thing new about POODLE versus previous known > vulnerabilities is the way to manipulate the known vulnerability to gain > the session cookie, which you can then re-use to log on to the site for > yourself without needing to authenticate. I