5 ms·

Case in point: MS making it more and more annoying to use IMAP. Hell, now you need to create oauth2 app just to login from non-approved client, as they recentl

by ilyt 3y ago

Case in point: MS making it more and more annoying to use IMAP. Hell, now you need to create oauth2 app just to login from non-approved client, as they recently forced OAUTH2 auth on IMAP clients. Sure thunderbird works but most lesser known clients require a lot of fuckery to make work (and possibly admin permissions for domain, not sure).

ggm 3y ago
https://github.com/simonrob/email-oauth2-proxy https://github.com/simonrob/email-oauth2-proxy "Just works" I run it with mbsync at the command line. You do need a client id and some interaction with your O365 admin.
- ilyt 3y ago
  This looks promising, thanks. I did the song and dance for claws-mail and one day it just... stopped working ;/
jojobas 3y ago
I would be migrating away (to anything) if my email provider pulled that on me.
- ilyt 3y ago
  It's entirely idiotic history. We had our own e-mail, but we had some problems that were generally caused by management wanting @example1.com and @example2.com to be entirely equivalent, not just an alias, but still land on the same account. which was fine for the email, as it can just have custom rules, but any related services like calendars bugged, as it saw different domains as different users. We tried to hack around it but it was still buggy in places. Boss finally got pissed off and decided to migrate to O365, all while IT was screaming nooo. "Because our clients use it too, it will be easier to collaborate" ...and it turned out that what he wanted isn't possible in O365 *fucking anyway* so all e-mails are under @example1.com. And we replaced some weird quirks with many more quirks we can't even hope to fix. We waste more time dealing with this shit than we did on running our own mail servers. Which we didn't like, coz running mail servers sucks, but O365 sucks harder.
alwayslikethis 3y ago
My university uses MS for their services, and they stubbornly refuse to let me use IMAP (not even with OAuth). I have to either use GNOME Evolution for Micro$oft exchange protocol or a proprietary app on my phone, which enforces bullshit control on a device I paid for.
- Spivak 3y ago
  > which enforces bullshit control on a device I paid for That's basically the raison d'etre. You, presumably a student, are getting caught in the crossfire of regulatory compliance and they don't want to maintain two email systems. Source: Used to be the one implementing those controls. We didn't like them either, I promise.
AnonC 3y ago
Effectively, MS has bulldozed companies that use Microsoft365 into using its own proprietary protocols and applications (Outlook). It scares companies into not enabling IMAP (even with OAuth2).

by ilyt 3y ago

ggm 3y ago

https://github.com/simonrob/email-oauth2-proxy https://github.com/simonrob/email-oauth2-proxy "Just works" I run it with mbsync at the command line. You do need a client id and some interaction with your O365 admin.

ilyt 3y ago
This looks promising, thanks. I did the song and dance for claws-mail and one day it just... stopped working ;/

jojobas 3y ago

I would be migrating away (to anything) if my email provider pulled that on me.

ilyt 3y ago
It's entirely idiotic history. We had our own e-mail, but we had some problems that were generally caused by management wanting @example1.com and @example2.com to be entirely equivalent, not just an alias, but still land on the same account. which was fine for the email, as it can just have custom rules, but any related services like calendars bugged, as it saw different domains as different users. We tried to hack around it but it was still buggy in places. Boss finally got pissed off and decided to migrate to O365, all while IT was screaming nooo. "Because our clients use it too, it will be easier to collaborate" ...and it turned out that what he wanted isn't possible in O365 *fucking anyway* so all e-mails are under @example1.com. And we replaced some weird quirks with many more quirks we can't even hope to fix. We waste more time dealing with this shit than we did on running our own mail servers. Which we didn't like, coz running mail servers sucks, but O365 sucks harder.

alwayslikethis 3y ago

My university uses MS for their services, and they stubbornly refuse to let me use IMAP (not even with OAuth). I have to either use GNOME Evolution for Micro$oft exchange protocol or a proprietary app on my phone, which enforces bullshit control on a device I paid for.

Spivak 3y ago
> which enforces bullshit control on a device I paid for That's basically the raison d'etre. You, presumably a student, are getting caught in the crossfire of regulatory compliance and they don't want to maintain two email systems. Source: Used to be the one implementing those controls. We didn't like them either, I promise.

AnonC 3y ago

Effectively, MS has bulldozed companies that use Microsoft365 into using its own proprietary protocols and applications (Outlook). It scares companies into not enabling IMAP (even with OAuth2).