#7 JMAP support

Closed
opened 9 months ago by epilys · 5 comments
epilys commented 9 months ago

This is a tracking issue for JMAP support which is WIP.

This is a tracking issue for JMAP support which is WIP. - [x] Authentication. (fastmail uses basic auth, and that's what is used in `meli` now ~~No standard way to authenticate has been published yet.~~ - [x] ~~Read special use roles for mailboxes from `Mailbox/query`. Requires `melib` support for special use autodiscover in backends.~~
epilys added the
enhancement
label 9 months ago
epilys added the
JMAP
label 9 months ago
arti commented 9 months ago
Fastmail has recently published their JMAP endpoint. https://jmap.topicbox.com/groups/fastmail-dev-beta/T83594f41ca76f56c/jmap-crash-course
epilys commented 9 months ago
Owner

@arti I’m afraid I don’t have a fastmail account! Thankfully there’s the Cyrus dev branch that has JMAP support and also the jmap proxy fastmail has published.

@arti I'm afraid I don't have a fastmail account! Thankfully there's the Cyrus dev branch that has JMAP support and also the jmap proxy fastmail has published.
arti commented 9 months ago

Would you be interested in a FastMail account for development purposes?
I would be willing to sponsor the account.

Would you be interested in a FastMail account for development purposes? I would be willing to sponsor the account.
epilys referenced this issue from a commit 9 months ago
epilys commented 9 months ago
Owner

@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 master now.

Thank you very much for the offer, really! 😃

@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 `master` now. Thank you very much for the offer, really! :smiley:
epilys added this to the release milestone 6 months ago
epilys commented 5 months ago
Owner

I have contacted fastmail support about their JMAP notification endpoint. Here’s part of the help ticket that describes the problem:

epilys writes:

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].
The URL
MUST contain variables called “types”, “closeafter”, and
“ping”.
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/” [..]

I have contacted fastmail support about their JMAP notification endpoint. Here's part of the help ticket that describes the problem: > ***epilys writes***: > > 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]. > The URL > MUST contain variables called "types", "closeafter", and > "ping". > 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/" [..]
epilys closed this issue 1 month ago
epilys modified the milestone from release to Full JMAP support 12 hours ago
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.