{
"using": [
"urn:ietf:params:jmap:core",
"com:linagora:params:jmap:firebase:push"],
"methodCalls": [[
"FirebaseRegistration/set",
{
"create": {
"4f29": {
"deviceClientId": "a889-ffea-910",
"token": "token1",
"types": ["Mailbox"],
"keys": {
"p256dh": "BM0HH37xD8sEh8NeiHu1hFuwxqeeruxPlX5S7XGWGjHY5UT5yZFQKAiihFQLP6GuEQPQOtD9z28HRyV7e1nndh8",
"auth": "uwPFKACOLBipGPTVz4UCDg"
},
"emailPush": {
"A1412": {
"filter": {
"operator": "OR",
"conditions": [
{ "inMailbox": "674cc240-95db-49ce-a8a2-054f4f733095" },
{ "hasKeyword": "$notify" }
]
},
"properties": ["from", "subject", "id"]
}
}
}
},
"c1"]]
}
Modify the current implem of Firebase jmap push to align with the new jmap email push spec defined here: https://datatracker.ietf.org/doc/draft-ietf-jmap-emailpush/
After implementing the data encryption part (see #2303 ), we would remain the EmailPush part: