Gmail will block all third party mail clients starting from June. That is, unless they pay $4500 minimum for an audit.

submitted by [deleted] from pmail.com

sorted by:
top
newinsightfulfun
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 insightful - 2 fun2 insightful - 1 fun3 insightful - 2 fun -  (2 children)

I have a website with an "email the mod" feature that was originally implemented using SMTP to a Gmail server. This worked- you had to turn on some "less secure clients" feature, but it worked.

At some point, Google started randomly turning off that feature. Then, when someone would use my "email the mod" feature, I'd get a "critical security alert!" telling me someone's login attempt had been blocked by GMail.

There was no rhyme or reason as to when this would happen, and it's just a great example of how computer "security" people are by and large complete narcissistic scumbags

[–]BravoVictor 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (1 child)

Yeah, I believe Google's policy has been to auto-deactivate the "less secure clients", e.g. the normal username/password authentication every user normally uses through the web UI, for scripts ever 6 months. I've run into that myself for some script automation I've written and it's really fucking annoying. Especially because the alternative, setting up Google API tokens, is a massive fucking PITA and is horribly documented and poorly supported.

[–][deleted] 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (0 children)

Is the API token thing even standard SMTP? I would hate to set up some non-standard thing just to support a single supplier that has already pissed me off.

At some point I'll probably either find or just set up a damned SMTP server. I swear, the security/privacy eggheads just ruin everything...