Any assistance would be greatly appreciated. Everything else is working save for that and its going to look silly to tell my boss, "We can run stats that inbox we just can't have a sub folder with a space in the name.

May I ask which version you are running your tests against?Perhaps your shell is removing or otherwise messing with your URL before it is sent to the server.You can see exactly what the server sees by looking in the /opt/zimbra/log/access_log.<today's date>

Setup account on mailbox user@zcs.dev / <password>Login through webclient and create a folder inside the Inbox named Spaced FolderSend a few emails to your own accountMove at least one email in to Spaced Folder

Request items in Spaced Folder using curl:

Note: The double quotes are to prevent the shell (in my case bash) from mangling the URL. The %20 encoding for a space character works in my case.

So what I found out is that this "&query=is:unread" is the difference between success and failure for me.

My zimbra version is: Zimbra 8.6.0_GA_1200 (build 20160606111426)

So basically if I try and query unread objects inside a folder with a space in the name, it fails. If it does not have a space it works.Now I can query the folder without the query option, and then just parse the json response, which is what I ended up doing.

Maybe someone else could try and verify the error and it could be reported as a bug.

Unfortunately as I have a working work around I'm not going to spend further time on the matter, if it is just me and my / our env that is fine. I'm not Ops and I don't have access to the host server/s. I'm just an emp tasked with putting together an email web monitoring dashboard and needed the rest API to work . Manually parsing the json response on the folder for the 'u' flag of an unread email is trivial and is fine for me. Maybe if someone else has this issue later they can do as you mention and see if they get the same result.