After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 615240 - enabling IDLE with imapx requires evolution restart
enabling IDLE with imapx requires evolution restart
Status: RESOLVED DUPLICATE of bug 207481
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[imapx]
Depends on:
Blocks:
 
 
Reported: 2010-04-09 00:34 UTC by Brian J. Murrell
Modified: 2010-09-30 09:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Brian J. Murrell 2010-04-09 00:34:36 UTC 
I have converted one of my IMAP accounts to use impax in hopes of seeing the IDLE functionality of the protocol in action.  My server support IDLE:

Response: CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE STARTTLS AUTH=GSSAPI SASL-IR

yet even after the initial connection and mailbox summary traffic, evolution never issues an IDLE command and enters the IDLE state.
Comment 1 dax 2010-04-09 06:08:34 UTC 
Under "Receiving Options" you have to check the box "Use Idle if the server supports it".

I think it should be checked by default with IMAPX.
Comment 2 Brian J. Murrell 2010-04-09 10:52:55 UTC 
Ahhh.  Didn't notice that.  Selected the option but had to completely quite evolution and restart for it to take affect.  Even going offline/online to force a new IMAP connection didn't help.  I will change the Summary of this bug to reflect that this is the actual bug here.
Comment 3 Milan Crha 2010-09-30 09:19:28 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 207481 ***