There's software like https://github.com/jmapio/jmap-perl you can use in front of your chosen provider but that seems like more headache than it's worth unless your imap implementation/lib is incredibly complicated.
Doing something like this is essentially a bet that your provider will eventually implement jmap.
They just need an IMAP/SMTP <-> JMAP bridge. This allows (small) providers to add support without much effort and there's suddenly a demand for clients (and vice versa good clients will increase demand for JMAP support).
The website lists jmap-proxy (https://github.com/jmapio/jmap-perl) Its age, technology choice and lack of documentation aren't exactly confidence inspiring, however.
Stalwart (https://github.com/stalwartlabs/imap-server/) seems to include a proxy feature (for both, though it's non-obvious to discover) and be better maintained.
A functioning proxy is make or break for me. If it works I can jump right into making a client, if it doesn't there's no point.
Wouldn't a JMAP bridge like [1] solve the same problems?
https://github.com/jmapio/jmap-perl seems the most similar to the project discussed here. Anyone have experience with it?