It was mentioned in the notes that the protocol engines may need to
be updated. I would add that JMAP, the successor to IMAP/SMTP without
IMAP's deficiencies is being actively worked on a pilot
implementations are already available iirc. A modern e-mail client is
going to need to handle this
I am on the JMAP mailing list although I must admit to paying attention to it only fitfully. It would perhaps be good if Hermes were an early adopter of JMAP.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am on the JMAP mailing list although I must admit to paying attention to
it only fitfully. It would perhaps be good if Hermes were an early adopter
of JMAP.
I am on the JMAP mailing list although I must admit to paying attention to
it only fitfully. It would perhaps be good if Hermes were an early adopter
of JMAP.
It was mentioned in the notes that the protocol engines may need to
be updated. I would add that JMAP, the successor to IMAP/SMTP without
IMAP's deficiencies is being actively worked on a pilot
implementations are already available iirc. A modern e-mail client is
going to need to handle this
https://jmap.io
I am on the JMAP mailing list although I must admit to paying attention to it only fitfully. It would perhaps be good if Hermes were an early adopter of JMAP.
https://datatracker.ietf.org/wg/jmap/about/
It doesn't look like a traditional C/C++ API
https://medium.com/linagora-engineering/why-jmap-is-the-future-of-emails-c63cd9106499
Maybe a little more esoteric:
But then again, I was never an IMAP expert.
Regards.
On Wed, Sep 12, 2018 at 6:48 PM Pete Maclean petemaclean@users.sourceforge.net wrote:
I'm not sure about the last one:
---- https://news.ycombinator.com/item?id=8785894
but google flagged it searching for JMAP.
Regards.
On Wed, Sep 12, 2018 at 7:14 PM Soren Bro sbrothy@users.sourceforge.net
wrote: