It seems that both Google and Microsoft need to be tricked to deal with company/institutional accounts correctly during the initial mailctl authorize phase.
To avoid having to use this trick, in particular, the awkward file renaming involved it would be nice to perform this behind the scenes by mailctl.
While that refactoring should not be too difficult, I feel that some further research is needed to see if this is exactly the same thing for both providers. Also, to check that the API-s are indeed that stupid or we are just overlooking something.
It seems that both Google and Microsoft need to be tricked to deal with company/institutional accounts correctly during the initial
mailctl authorize
phase.The trick was initially discovered here https://github.com/pdobsan/mailctl/issues/5#issuecomment-1209008661 by @ferdinandyb then successfully used (or rediscovered) by others.
To avoid having to use this trick, in particular, the awkward file renaming involved it would be nice to perform this behind the scenes by
mailctl
.While that refactoring should not be too difficult, I feel that some further research is needed to see if this is exactly the same thing for both providers. Also, to check that the API-s are indeed that stupid or we are just overlooking something.