Hello Aki, The Smartermail don't support IDLE command at CAPABILITY:
Dovecot: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. Smartermail: * CAPABILITY IMAP4rev1 AUTH=CRAM-MD5 UIDPLUS QUOTA XLIST CHILDREN In this case, would not the because Dovecot send the IDLE command to SmarterMail. -----Mensagem original----- De: dovecot [mailto:dovecot-boun...@dovecot.org] Em nome de Aki Tuomi Enviada em: terça-feira, 23 de agosto de 2016 13:25 Para: dovecot@dovecot.org Assunto: Re: Possible IMAP IDLE bug in Dovecot 2.2.18 and 2.2.25 On 23.08.2016 19:15, Aki Tuomi wrote: > > > On 23.08.2016 15:08, cleber-lis...@inetweb.com.br wrote: >> Hello Guys, >> I guess that I found a bug in Dovecot 2.2.18 and 2.2.25 versions. >> The problem it's when I try to connect in a Dovecot used a proxy to >> another e-mail server (in our case it's a Smartermail Server) the >> DoveCot send a lot of IDLE commands to the destination server. With >> that, the LOG files grow and grow and grow :( >> I make a test with 1 connection only and if you see the log file >> in the same second the dovecot send 25, 40 IDLE commands. But, when I >> disconnect the client (outlook 2013) the dovecot continue to send the >> IDLE command for some seconds. >> If I try to connect directly to Smartermail with Outlook this >> don't occurrs. >> > > Just to be sure, the behaviour you are expecting is that IDLE is not > used, right? > > Aki Also, looking at the code, IDLE is only used if your server claims to understand it, so could you do following: telnet backend-host backend-port a CAPABILITY a LOGIN username password a CAPABILITY a LOGOUT and provide the output. Aki
