You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's my understanding that JMAP offers a similar client/server protocol but has gone through intensive usage at Fastmail, is implemented in Cyrus and Apache James while Dovecot is working on it (although, not entirely sure of status).
Although, perhaps it's simply my misunderstanding and TMTP is more targeted to server-to-server communication? I still think it would probably be a good idea to take inspiration and/or try to consolidate the efforts and take definitions from there.
Sorry if it's inappropriate!
The text was updated successfully, but these errors were encountered:
JMAP fits between email apps (MUAs in the lingo) and email hosts, synchronizing user accounts both ways, much like IMAP. It has optimizations for mobile apps. It extends the email ecosystem; it's not trying to solve the fundamental problems that TMTP addresses.
TMTP doesn't define any server-to-server communication. See the new FAQ for details.
It's my understanding that JMAP offers a similar client/server protocol but has gone through intensive usage at Fastmail, is implemented in Cyrus and Apache James while Dovecot is working on it (although, not entirely sure of status).
It's also an IETF spec, see RFC8620 RFC8621 RFC8887
Although, perhaps it's simply my misunderstanding and TMTP is more targeted to server-to-server communication? I still think it would probably be a good idea to take inspiration and/or try to consolidate the efforts and take definitions from there.
Sorry if it's inappropriate!
The text was updated successfully, but these errors were encountered: