So syncing between my mail client and mail clients from other people will be as frickle as ever. What this project aims to do right is offline mode and syncing between multiple instances of my mail client.
I'd like to keep my front-end as absolutely light as possible, so I'm foregoing gwt/bootstrap and going with mostly just handwritten jquery.
This project is also written in Go. I have IMAP go-routines which will send changes on the IMAP server to a gateway multiplexer which stores those changes in a synchronize-able DB. The Webgui will listen for changes from the DB and present them to the user. I chose to go this route such that i can run the gateway and the webgui on different computers both with a local copy of the DB and have them synchronize when network connectivity is present.
I've opted for GWT because i like static typing. From a performance perspective, i've never really found much difference between GWT and hand-written JS.
I still cannot successfully MIME-parse all of my emails, but the ones that fail are spam (and also don't work in Outlook 2011) so i'd say it's the email's fault.
I can recommend Google Go for tasks such as IMAP because of its concurrency model. You can run a go-routine for each IMAP connection and their idea of agents communicating through channels worked really well for my IMAP client.
mail at hajo (dot) me