search

randomouscrap98 / contentapi

A generic content system to make some kinda standard websites
GNU General Public License v3.0
9 stars 2 forks source link

Handle expiring third party email access #101

Closed randomouscrap98 closed 2 years ago

randomouscrap98 commented 2 years ago

Our standard password-based access will be disabled on May 31st for smilebasicsource@gmail.com. Google suggests using some kind of application id api thing, which might be perfectly doable.

Research regarding this will be placed here. First is the link in the email itself: (oops, there was none, thanks google!). Or, use oath: https://www.emailarchitect.net/easendmail/sdk/html/object_oauth.htm

Oh here's a page: https://support.google.com/accounts/answer/6010255

randomouscrap98 commented 2 years ago

Google's OAuth nightmare is... well, a nightmare, and I just don't want to navigate that mess. Something about needing to verify using the special google webpage, which doesn't work on servers, and ugh I'm sure there's some way but if it's hidden that badly to begin with, I don't trust whatever new method they've come up with to persist for any length of time.

randomouscrap98 commented 2 years ago

I've set up an SES (Amazon) email account and will try to use that, but they've rejected our production level access, which is needed to you know... actually send emails. My email was rather strongly worded, plus around the same time I sent feedback on the AWS console, and I'm betting it's not anonymous, and I may have said some nasty things, so if some petty employee decides to just... be bad, that might not be a route either. Plus, they have VERY STRICT bounce rules and we might get banned anyway, so... ugh

randomouscrap98 commented 2 years ago

SES has accepted us... for now.