This? https://en.wikipedia.org/wiki/JSON_Meta_Application_Protocol They cited IMAP's complexity, high resource use, JMAP is implemented using JSON APIs over HTTP They complain about complexity, then add another two layers of complexity in their own protocol? I think POP3 is the simplest standard, and have also written a basic IMAP client. Parsing IMAP isn't as easy as a binary protocol, but it's definitely not at the…
POP3 has no locking. It won't work with multiple clients, and that is awful. But I agree with your assessment. We need good utilities which make JSON human-readable, and which turn human-readable into JSON. Might as well not use JSON, except for internal traffic.
JSON is only excusable if your protocol is designed for webmail clients. Otherwise this is a case of the emperor having no clothes.