# Sudden gmail SMTP authentication Error

**URL:** <https://forum.inductiveautomation.com/t/sudden-gmail-smtp-authentication-error/105775>\
**Category:** General Discussion\
**Created:** [May 1, 2025, 12:38pm UTC](https://forum.inductiveautomation.com/t/sudden-gmail-smtp-authentication-error/105775 "2025-05-01T12:38:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mattn1](https://avatars.discourse-cdn.com/v4/letter/m/54ee81/32.png) [@mattn1](https://forum.inductiveautomation.com/u/mattn1)\
**Post date:** [May 1, 2025, 12:38pm UTC](https://forum.inductiveautomation.com/t/sudden-gmail-smtp-authentication-error/105775/1 "2025-05-01T12:38:09Z")

</div>

I have several customers using a gmail email server. They have been on the server for years. I have confirmed that 2 step verification login is disabled and less secure apps are enabled.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/5/d5cfd92296f6c8343f512ef4072bdcb0f42554ce.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/b/0b541f633bb7334c46ef120dcb1a0622e6f0d9c5.png)

Password is the same as it has been, login has been the same as it has been. Has there been a recent change at gmail, anyone else suddenly experiencing this issue?

here is the error from the email server test on the gateway.  
javax.mail.AuthenticationFailedException: 535-5.7.8 Username and Password not accepted. For more information, go to  
535 5.7.8 [https://support.google.com/mail/?p=BadCredentials](https://support.google.com/mail/?p=BadCredentials) 00721157ae682-708c467f584sm1438877b3.83 - gsmtp

---

<div class="post-metadata">

**Author:** ![Cody\_Morgan](https://avatars.discourse-cdn.com/v4/letter/c/db5fbb/32.png) [@Cody\_Morgan](https://forum.inductiveautomation.com/u/Cody_Morgan)\
**Post date:** [May 1, 2025, 7:42pm UTC](https://forum.inductiveautomation.com/t/sudden-gmail-smtp-authentication-error/105775/2 "2025-05-01T19:42:23Z")

</div>

Looks like Google pulled support for this today?

> **[Beginning September 30, 2024: third-party apps that use only a password to...](https://workspaceupdates.googleblog.com/2023/09/winding-down-google-sync-and-less-secure-apps-support.html)**
>
> \[Update - April 29, 2025\]:  Less Secure Apps will no longer be supported as of May 1, 2025. \[Update - February 12, 2025\]:  Less Secure Apps ...

---

<div class="post-metadata">

**Author:** ![mattn1](https://avatars.discourse-cdn.com/v4/letter/m/54ee81/32.png) [@mattn1](https://forum.inductiveautomation.com/u/mattn1)\
**Post date:** [May 1, 2025, 8:23pm UTC](https://forum.inductiveautomation.com/t/sudden-gmail-smtp-authentication-error/105775/3 "2025-05-01T20:23:56Z")

</div>

Well that would explain why. Thanks!

I was eventually able to set them up with new passwords via the gmail app passwords feature.

---

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [May 1, 2025, 9:11pm UTC](https://forum.inductiveautomation.com/t/sudden-gmail-smtp-authentication-error/105775/4 "2025-05-01T21:11:01Z")

</div>

Alternatively, you can also setup an OAuth2 SMTP Profile. This uses Ignition's OAuth2 Client facility to acquire and maintain a valid access token for interacting with, in your case, Google Mail API.

One advantage of this is that you can more granularly control the access. For example, one of the [available scopes for Gmail API](https://developers.google.com/workspace/gmail/api/auth/scopes) is send-only--the token cannot be used to read e-mails.

Here are some references if you (or others!) wish to further explore this route:

- [OAuth2 SMTP Profiles](https://docs.inductiveautomation.com/docs/8.1/platform/gateway/config/email-settings#oauth2-smtp)
- [OAuth2 Clients](https://docs.inductiveautomation.com/docs/8.1/platform/security/oauth-2-clients)
