Hi ellie,
On Monday, 15 May 2017 08:32:30 CEST ellie timoney wrote:
> Planning to cut a release straight from the 2.4 git HEAD at time of
> writing (bfc80b3). The release tarball is already built and uploaded at
> https://cyrusimap.org/releases/cyrus-imapd-2.4.19.tar.gz
>
> If you could give tha
Hi Thomas,
Planning to cut a release straight from the 2.4 git HEAD at time of
writing (bfc80b3). The release tarball is already built and uploaded at
https://cyrusimap.org/releases/cyrus-imapd-2.4.19.tar.gz
If you could give that a run through your test suite, that'd be amazing.
If it works ok
Hi Ellie,
On Tuesday, 09 May 2017 03:15:07 CEST ellie timoney wrote:
> I'm looking at doing a new release of 2.4 soon -- there's been a number
> of issues coming up lately which are already fixed in git, but aren't in
> a released version. It might save some support effort if these fixes
> were r
Hi Thomas, Philipp,
On Tue, Oct 4, 2016, at 05:19 PM, Thomas Jarosch wrote:
> we also have a version of this patch for cyrus 2.4 in production now.
> If you're interested, we can upstream it, too.
Sorry for the late reply, but this would be great!
I'm looking at doing a new release of 2.4 soon -
Hi Ellie,
On Tuesday, 4. October 2016 11:02:39 ellie timoney wrote:
> This version of the patch is now on master. Thanks very much for
> putting it together :)
nice :) Thanks.
> I've opened https://github.com/cyrusimap/cyrus-imapd/issues/42 for
> backporting it to 2.5 -- expecting to do it soon
This version of the patch is now on master. Thanks very much for
putting it together :)
I've opened https://github.com/cyrusimap/cyrus-imapd/issues/42 for
backporting it to 2.5 -- expecting to do it soon, but making sure it
doesn't get forgotten if I get distracted!
Cheers,
ellie
On Thu, Sep 2
Certainly and my apologies. I did not realize the distinction in the
threads.
Andy
On 09/27/2016 06:15 PM, ellie timoney via Cyrus-devel wrote:
Can we please continue the analysis of your situation in your thread,
and let this thread be about the patch?
Hi Andy,
At this stage the proposed patch only applies to master, whereas in your
thread on info-cyrus you mention you're on 2.5.9.
I do consider this patch -- once landed on master -- to be a possible
candidate for back porting to 2.5, but we're not at that stage yet.
Can we please continue the
Don't know if my vote counts, but we are still accumulating over 100
idled connections every 24 hours from two accounts being checked by an
old (+5 yrs) BlackBerry.
So I believe an idled timeout could help us there.
Due to my workload I have not been able to do any network sniffing on
the Bla
On Thu, Sep 22, 2016, at 01:29 AM, Philipp Gesang wrote:
> Minutes again, because IMO a fallback between different units of
> measure would be confusing.
Yeah, I was thinking the same thing. :) The updated patch looks good to
me.
So it looks like what we're getting from this is two things:
* ma
-<| Quoting Philipp Gesang , on Wednesday,
2016-09-21 17:26:40 |>-
> Use the value of the configuration variable “timeout” as an upper
> limit in minutes for idle connections.
^^^
Minutes again, because IMO a fallback between different units of
measure would be confusing.
Best,
P
11 matches
Mail list logo
