There is so much NIH going on in this protocol, it's as if the authors we're completely unaware of modern HTTP API design.
They're not just doing IMAP over http, they invented their own error bodies, schema's , negotiation and RPC.
They're not just doing IMAP over http, they invented their own error bodies, schema's , negotiation and RPC.
They even essentially say that HTTP is not necessary to their protocol, so I think it's pretty apparent that HTTP is a utilitarian choice, but they're not trying to build email-over-http.
SOAP had same rationalization.