3 ms·
I have worked for exactly one company in my entire decade-ish long career that mandated how I connect to email / disabled IMAP, and have exceedingly little pati
by klardotsh 3y ago
I have worked for exactly one company in my entire decade-ish long career that mandated how I connect to email / disabled IMAP, and have exceedingly little patience for places that would disable IMAP without strong reason (for example a law firm or health care company, I could understand, but for the vast majority of companies? A policy mandating that laptops and phones must be encrypted at rest and locked with secure passphrases is going to do more than mandating that I connect to the Gmail web interface rather than the Gmail IMAP interface from the same exact machine on the same exact network - especially if "app passwords" to bypass 2FA have to expire periodically, which I'd also find reasonable)
- davkan 3y agoI managed O365 for my last employer and we enforced exchange login. Granted we were part of the defense industrial base and would fall under your exceptions, certainly. But, if a company is making even a minimal effort to prevent company data ending up on unmanaged devices its a nobrainer to disable imap, as much as it sucks for the end user. In the end we did have to make singular exceptions for certain developers because outlook’s absolutely pathetic plaintext support was causing issues when they were contributing via the LKML. But that was a significant business justification as opposed to a workflow optimization.