ehind IDLE-less capability is
but I am under direction not to enable it.
Thanks again all,
R.
> Date: Tue, 23 Nov 2010 14:36:47 -0800
> From: david.l...@digitalinsight.com
> To: r...@fastmail.fm
> CC: prout...@hotmail.com; i...@sussex.ac.uk; info-cyrus@lists.andrew.cmu.edu
> Subje
On Wed, 24 Nov 2010, Robert Mueller wrote:
>> I was asked by IT to not permit IDLE since the current server went down
>> after 4-500 blackberries ate up all the (limited) capabilities of that
>> machine.
>
> I'd really be surprised if that was a problem these days. We have
> machines that have 100
> I was asked by IT to not permit IDLE since the current server went down
> after 4-500 blackberries ate up all the (limited) capabilities of that
> machine.
I'd really be surprised if that was a problem these days. We have
machines that have 1 connections quite fine. Yes they're fairly
load
On Tue, Nov 23, 2010 at 10:01:58AM -0500, Ron Vachiyer wrote:
> I believe there was an issue as well where POP clients using outlook would
> cause mailbox corruption when they popped a mailbox being maintained by a
> blackberry connected via IMAP.
Not in 2.4.x there shouldn't be. The locking
>
>> -Chris
>>
>> On 11/23/2010 10:01 AM, Ron Vachiyer wrote:
>>>
>>>
>>> > Date: Tue, 23 Nov 2010 14:44:34 +
>>> > From: i...@sussex.ac.uk
>>> > To: prout...@hotmail.com; info-cyrus@lists.andrew.cmu.edu
>>>
On 23/11/10 10:01 -0500, Ron Vachiyer wrote:
>Hello,
>
>I won't argue since clearly I am in the minority ;) Using courier-imap on
>our Plesk servers, TCP/143 is closed after every new mail verification. A
>dovecot server I checked does the same. Cyrus seems to allow the session
>to be maintained
11/23/2010 10:01 AM, Ron Vachiyer wrote:
>>
>>
>> > Date: Tue, 23 Nov 2010 14:44:34 +
>> > From: i...@sussex.ac.uk
>> > To: prout...@hotmail.com; info-cyrus@lists.andrew.cmu.edu
>> > Subject: Re: disable IMAP IDLE
>> >
>> >
>
--On 23 November 2010 10:01:58 -0500 Ron Vachiyer
wrote:
>
>> I thought sessions remained open for efficiency, regardless of IDLE,
>> until closed by the client or 30 minutes have elapsed.
>>
>> IDLE just lets the server notify the client if new email arrives,
>> doesn't it?
>>
>> Even witho
new email notification.
-Chris
On 11/23/2010 10:01 AM, Ron Vachiyer wrote:
> Date: Tue, 23 Nov 2010 14:44:34 +
> From: i...@sussex.ac.uk
> To: prout...@hotmail.com; info-cyrus@lists.andrew.cmu.edu
> Subject: Re: disable IMAP IDLE
>
>
>
> --On 22 November 2010 18:4
> Date: Tue, 23 Nov 2010 14:44:34 +
> From: i...@sussex.ac.uk
> To: prout...@hotmail.com; info-cyrus@lists.andrew.cmu.edu
> Subject: Re: disable IMAP IDLE
>
>
>
> --On 22 November 2010 18:40:37 -0500 Ron Vachiyer
> wrote:
>
> >
> > Hello,
>
--On 22 November 2010 18:40:37 -0500 Ron Vachiyer
wrote:
>
> Hello,
>
> I thought it was possible in Cyrus to disable the IDLE functionality,
> either with imapidlepoll: 0 in imapd.conf, or by commenting idled in
> cyrus.conf. However, having both disabled, clients still connect and
> maintai
--On Tuesday, November 23, 2010 9:15 -0500 Ron Vachiyer
wrote:
> No it isn't, I had already checked and strangely it is notwhich is
> really surprising me that the sessions remain;
A client can keep a session open by sending NOOP every 25 minutes.
If you won't allow IDLE that's probably
Date: Tue, 23 Nov 2010 08:57:52 -0400
From: bouti...@ednet.ns.ca
To: info-cyrus@lists.andrew.cmu.edu
Subject: Re: disable IMAP IDLE
On 11/23/2010 08:52 AM, Ron Vachiyer wrote:
> >From how I understand the RFC, if no IMAP IDLE capability is
> advertised, the client should not attempt
ion, they seem to when Cyrus is
the IMAP server.
Is your server advertising IDLE ?
telnet to port 143 and issue this command:
. CAPABILITY
R.
> Date: Tue, 23 Nov 2010 06:38:28 +0100
> Subject: Re: disable IMAP IDLE
> From: simon.mat...@invoca.ch
> To: prout...@hotmail.
is the IMAP server.
R.
> Date: Tue, 23 Nov 2010 06:38:28 +0100
> Subject: Re: disable IMAP IDLE
> From: simon.mat...@invoca.ch
> To: prout...@hotmail.com
> CC: info-cyrus@lists.andrew.cmu.edu
>
> >
> > Hello,
> >
> > I thought it was possible in Cy
>
> Hello,
>
> I thought it was possible in Cyrus to disable the IDLE functionality,
> either with imapidlepoll: 0 in imapd.conf, or by commenting idled in
> cyrus.conf. However, having both disabled, clients still connect and
> maintain their socket open on tcp 143. Is it not possible or am I g
Hello,
I thought it was possible in Cyrus to disable the IDLE functionality, either
with imapidlepoll: 0 in imapd.conf, or by commenting idled in cyrus.conf.
However, having both disabled, clients still connect and maintain their socket
open on tcp 143. Is it not possible or am I going abou
17 matches
Mail list logo
