This is a tracking issue for JMAP support which is WIP.
Fastmail has recently published their JMAP endpoint.
@arti That’s very kind of you. I got a trial account and have tested the implementation on fastmail’s endpoint. It can authenticate, fetch mailboxes and email currently. I merged the
jmap branch and it’s available in
Thank you very much for the offer, really! 😃
I have contacted fastmail support about their JMAP notification endpoint. Here’s part of the help ticket that describes the problem:
According to rfc8620 the Session object returned by a
JMAP server must contain an eventSourceUrl field that
contains the url...:
" The URL to connect to for push events, as described in
Section 7.3, in URI Template (level 1) format [RFC6570].
MUST contain variables called “types”, “closeafter”, and
The use of these variables is described in Section 7.3.”
[..] Right now I’m connecting to jmap.fastmail.com and the
eventSourceUrl is “https://jmap.fastmail.com/event/” [..]
Deleting a branch is permanent. It CANNOT be undone. Continue?