Re: fetchmail and JMAP protocol

Am 26.03.19 um 06:24 schrieb Ranjan Maitra:
> On Mon, 25 Mar 2019 11:01:30 +0100 Matthias Andree <[email protected]> wrote:
>
>> Am 21.03.19 um 02:28 schrieb Ranjan Maitra:
>>> Hi,
>>>
>>> I apologize if this is an ill-formed question, but I am looking for leads. Outlook's protocol that works with OAUTH2 OTP verification seems to come with e-mails downloaded in json format. Poking around brought me to the JMAP protocol. I was wondering if fetchmail can handle it, or if there are some other ways of processing mail extracted in json format (we have successfully obtained ways to get this).
>> Fetchmail supports the documented IETF protocols for mail retrievals,
>> dominantly POP3 and IMAP. No JMAP, no HTTP-/REST-based stuff, no
>> proprietary protocols.
> Thanks, FWIW, JMAP is IETF protocol as per https://github.com/jmapio/jmap and seeks to replace IMAP+SMTP. I do not know much about it, but at least the spec is published on github.
>
> I did not see this as being a proprietary protocol.

That was just an enumeration since other questions often go towards
supporting Microsoft or whoever else's inventions. The MAPI contribution
was a one-shot from a Google Summer of Code that has fallen to bit-rot
even before being integrated to a release, and I don't intend to make
such a mistake again. PWMD, a side feature to many however, shows an
entirely different model, I receive frequent updates.

JMAP isn't an IETF standard or even in RFC form yet, it's in draft stage
and I don't have a single JMAP server that I could use, let alone two
different implementations to test against. Given the current maintenance
capacity for fetchmail it's no good adding moving targets. Ask again if
it's matured to RFC stage, has a sufficient user base, and there are two
different server-side implementations that I can test against without
paying.