On Thu, Dec 08, 2011 at 10:00:26AM -0800, Andrew Morgan wrote: > So, I tried adding all the new 2.4 capabilities to the > suppress_capabilities setting. I found that if I added URLAUTH=BINARY to > suppress_capabilities, I was unable to establish an IMAP connection to the > frontend. imtest didn't print any output, and proxyd on the frontend was > spinning at 100% cpu. If I remove URLAUTH=BINARY from > suppress_capabilities, leaving all the other new capabilities suppressed, > it works fine. I'm not sure if this is a bug... Let me know if I should > file it as a bug.
Meep - sorry, it's a bug. Fixed on master. I really REALLY need to take some time fixing stable. > suppress_capabilities: ESEARCH LIST-EXTENDED QRESYNC WITHIN XLIST ENABLE > SORT=DISPLAY > > The imapd.conf manpage says I only need: > > suppress_capabilities: ESEARCH QRESYNC WITHIN XLIST LIST-EXTENDED > > if I have 2.3 murder backends. Is that correct, or should I suppress the > new ENABLE and SORT=DISPLAY too? Probably should suppress SORT=DISPLAY. That's even newer than the imapd.conf docs! I think ENABLE is OK, because clients are expected to handle NO responses. Bron. ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
