3 ms·
> Less secure access also enables using software running on your own computer to access your email easily. For example offlineimap and imapfilter. In theory it
by jefftk 5y ago
> Less secure access also enables using software running on your own computer to access your email easily. For example offlineimap and imapfilter. In theory it ought to work with OAuth but damned if I can get it to work and any instructions a few years old are useless because something has changed in the interim.
You shouldn't need OAuth; have you tried application-specific passwords (https://support.google.com/accounts/answer/185833 https://support.google.com/accounts/answer/185833)?
- michaelmrose 5y agoIf this is an effective workaround why is it useful to disable the feature in the first place. It seems like a 16 digit password this is actually much less secure than the current state of affairs. It's probably not much worth exploring because I'm also having to migrate off of legacy google apps for your domain as well.
- rstuart4133 5y agoOh, so you still support application specific passwords. I couldn't find them when I last looked, or maybe it was because applications just moved to the OAuth2 model and didn't offer the option. I'm pretty sure Thunderbird's calendar extension doesn't. I didn't ever understand why Google allowed you to enter a password into a random piece of software. In fact I'm still somewhat perplexed by them letting you enter it into a browser, but I guess they could be using the browser DRM module to get some assurance they are dealing with software they can trust. I guess it's just too hard to make move everything to hardware security tokens. Nonetheless, I don't see an choice in the long term - physical security tokens that don't allow firmware upgrades is where we must end up.