Re:IMAP API – self hosted daemon to access IMAP and SMTP acc...
by josephg on Thursday December 10, 2020 @03:42PM
(#25378344)
JMAP is definitely more complicated, but that complexity enables some very useful features. You can search, you can fetch emails by thread. You can get text snippets of emails for preview. JMAP can also automatically convert any email into directly renderable HTML (or plain text).
I’m convinced if nothing else the jmap json format is what everyone should be using for passing around email objects since it’s so well designed and feature rich. Almost all hand rolled email json formats throw away data you really want when rendering or processing email messages.
IMAP api does look lovely though.
Re:IMAP API – self hosted daemon to access IMAP and SMTP acc...
by rmccue on Thursday December 10, 2020 @08:29PM
(#25381213)
I tried using the JMAP bridge to develop a modern client as you mention, but there were huge problems with it. It appears to be abandoned, and Fastmail’s demo install of it is entirely broken too.
I ended up using the underlying lib that this project uses (also by andris9) and have had basically no problems whatsoever, it was a night and day difference.
Re:IMAP API – self hosted daemon to access IMAP and SMTP acc...
by inputmice on Thursday December 10, 2020 @04:05PM
(#25378663)
> If your use-case is just wanting to fetch emails from a bunch of inbox folders in real-time, potentially with some querying/filtering,
Nobody says you need to implement all of JMAP (from a client perspective). Just implement Email/query Email/get
imapapi, in my opinion, being a RESTful API, appears to have a much simpler surface, seems easier to play with using curl, and if you're developing a bunch of RESTful services that use Swagger, it fits better with your stuff. So, less dev-time to use :-)