disable IMAP IDLE

[Patrick Boutilier]

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 to use it and should close the
> TCP socket after every operation. Backberry connections to courier-imap
> and dovecot will not maintain a TCP session, 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.matter at invoca.ch
>  > To: proutfoo at hotmail.com
>  > CC: info-cyrus at lists.andrew.cmu.edu
>  >
>  > >
>  > > 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
>  > > about it wrong?
>  >
>  > I may be completely wrong but as I understand it the IMAP client may
>  > always keep connection on port 143 established, IDLE just changes the way
>  > how the client learns about new messages and such.
>  >
>  > Regards,
>  > Simon
>  >
>
>
>
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: boutilpj.vcf
Type: text/x-vcard
Size: 286 bytes
Desc: not available
Url : http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20101123/9e218dd8/attachment.vcf