[JMAP] Re: I-D Action: draft-ietf-jmap-emailpush-03.txt

["Matthew Horsfall (alh)" <[e-mail]>]

On Sun, May 3, 2026 at 9:38 PM <[e-mail]> wrote:

> Internet-Draft draft-ietf-jmap-emailpush-03.txt is now available. It is a
> work
> item of the JSON Mail Access Protocol (JMAP) WG of the IETF.
>

One nit:

The urn:ietf:params:jmap:emailpush capability support for the extensions to
PushSubscription described in this document


This should probably be "The urn:ietf:Params:jmap:emailpush capability
*adds* support for...".

I also have a question about the design / intended use. The spec says:

*emailPush*: Id[EmailPushConfig]|null If not null, this is a map. The keys
are Account ids for accounts with support for the
urn:ietf:params:jmap:emailpush capability. The server will push EmailPush
objects for these accounts when a new message arrives, in accordance with
the associated EmailPushConfig options for the account.

So... a single account can only have a single configuration that is a list
of various filters, and then a list of properties to fetch for anything
matching those filters.

Is that not too restrictive? It means that you can't have different
filters/properties combinations -- imagine you have one mailbox you want
previews for anything that comes in, but for another mailbox you only want
subjects, or to even know a new message has arrived.

The client can post-filter this, but then we're wasting resources/bandwidth
providing data not wanted.

-- Matthew Horsfall (alh)