IMAP: "BAD parse error: illegal character in quoted string"
Over the weekend, I upgraded my FOSS instance of Zimbra from 8.0.2 to 8.0.3. I've been using Zimbra for years on this one server, and it's worked great (sans a few mysterious issues, like the one I'm about to report).
Anyway, after the upgrade (which went fine), I noticed that IMAP now has a problem. I'm not sure if it's all users, some users, or just me, but my Apple Mail client suddenly began prompting me for the password over and over and saying it could not connect to the IMAP server. I have enabled logging with zmprov addAccountLogger email@example.com zimbra.imap debug, and began watching the mailbox.log file for ImapServer entries.
It seems that every time Apple Mail prompts me for my password and I enter it, I see this in the log immediately after:
Note: The illegal character in question varies.
2013-03-25 10:19:15,648 INFO [ImapServer-6]  imap - [172.16.144.13] connected
2013-03-25 10:19:15,649 WARN [ImapServer-6]  imap - BAD parse error: illegal character '¡' in quoted string
2013-03-25 10:19:15,650 INFO [ImapServer-6]  imap - Handler exiting normally
2013-03-25 10:39:15,518 INFO [ImapServer-13]  imap - [172.16.144.13] connected
2013-03-25 10:39:15,519 WARN [ImapServer-13]  imap - BAD parse error: illegal character '°' in quoted string
2013-03-25 10:39:15,520 INFO [ImapServer-13]  imap - Handler exiting normally
2013-03-25 10:39:15,626 INFO [ImapServer-13]  imap - [172.16.144.13] connected
2013-03-25 10:39:15,628 WARN [ImapServer-13]  imap - BAD parse error: illegal character 'á' in quoted string
2013-03-25 10:39:15,629 INFO [ImapServer-13]  imap - Handler exiting normally
During my several hours of troubleshooting, I decided to disable the Zimbra proxy and set the IMAP and POP3 services back to their normal ports. This caused the error to go away. Upon re-enabling the proxy, the problem is back. Does Nginx have its panties in a wad?
I also stumbled upon another thread here where setting zmlocalconfig -e nio_imap_enabled=false seemed to help a particular IMAP client, so I thought I'd try it. It worked, although Apple Mail continues to prompt me for my password at least mail was being read from the server. To verify, I set the property back to true, and the problem returned. So, I set the property back to false, but the problem remains, so apparently NIO doesn't have anything to do with it.
After two days of troubleshooting, I think I'm officially stumped. Ideas?