Sending Email via Gmail changing for May 30
I got an email from Google saying on May 30 apps that use user name and password won't be able to send email via Gmail. We need to change to either of two options:
1) Sign in with Google
2) OAuth 2.0
Any idea how to do either of these with VB6? Or failing that, any other suggestions? It's way over my head for sure.
Many thanks in advance for any assistance.
Re: Sending Email via Gmail changing for May 30
Looks like these guys have a reasonably priced commercial solution. Anybody have any experience with it? Does it work well?
https://www.emailarchitect.net/easendmail
Re: Sending Email via Gmail changing for May 30
i use smtp2go (free for limited numbers of emails) as a smtp server, mostly without problems, using CDO.message, i prefer to avoid using gmail for automated sending of emails
Re: Sending Email via Gmail changing for May 30
Quote:
Originally Posted by
westconn1
i use smtp2go (free for limited numbers of emails) as a smtp server, mostly without problems, using CDO.message, i prefer to avoid using gmail for automated sending of emails
Looks like a great service but it requires a "work" email to sign up for the free account. Most of my customers who use Gmail don't have a work email. I wonder if there's any way around that?
Re: Sending Email via Gmail changing for May 30
@ westconn....any idea # of smtp2go's limited emails for free? I send myself UP TO 2 dozen emails to remind me of friends' birthdays and anniversaries...usually around20 or so a day, but can be a longer list.
Sami
Re: Sending Email via Gmail changing for May 30
Quote:
Originally Posted by
Darkbob
We've used this for years and it works well and is easy to use. Documentation is pretty good and the samples give a nice starting point.
Re: Sending Email via Gmail changing for May 30
Quote:
Originally Posted by
Darkbob
I got an email from Google saying on May 30 apps that use user name and password won't be able to send email via Gmail. We need to change to either of two options:
1) Sign in with Google
2) OAuth 2.0
Any idea how to do either of these with VB6? Or failing that, any other suggestions? It's way over my head for sure.
Many thanks in advance for any assistance.
Google has been hinting at this for over a year now. At the time it was targeting "Less Secure Apps", and I subsequently opted for "2-Step Verification" with a Google provided 16 byte pass code. Is this still the case, as I have not been informed of any such action.
J.A. Coutts
Re: Sending Email via Gmail changing for May 30
J.A. --- this is the email sent by Google...maybe you can interpret/advise?
On May 30, you may lose access to apps that are using less secure sign-in technology
your email @ gmail
To help keep your account secure, Google will no longer support the use of third-party apps or devices which ask you to sign in to your Google Account using only your username and password. Instead, you’ll need to sign in using Sign in with Google or other more secure technologies, like OAuth 2.0. Learn more
What do you need to do?An app or device which uses Simple Mail Transfer Protocol (SMTP) to send emails using your Google Account has less secure access to your Gmail. This might be an older device, like a printer or scanner. To continue using your Google Account with this app or device:
- App - Remove your Google Account from the app or device and sign in again using Sign in with Google
- Device - Change your device’s settings so you’re using more secure sign-in technology
Re: Sending Email via Gmail changing for May 30
Quote:
Originally Posted by
SamOscarBrown
J.A. --- this is the email sent by Google...maybe you can interpret/advise?
On May 30, you may lose access to apps that are using less secure sign-in technology
your email @ gmail
To help keep your account secure, Google will no longer support the use of third-party apps or devices which ask you to sign in to your Google Account using only your username and password. Instead, you’ll need to sign in using Sign in with Google or other more secure technologies, like OAuth 2.0. Learn more
What do you need to do?An app or device which uses Simple Mail Transfer Protocol (SMTP) to send emails using your Google Account has less secure access to your Gmail. This might be an older device, like a printer or scanner. To continue using your Google Account with this app or device:
- App - Remove your Google Account from the app or device and sign in again using Sign in with Google
- Device - Change your device’s settings so you’re using more secure sign-in technology
According to Google support:
-----------------------------------
To help keep your account secure, starting May 30, 2022, Google will no longer support the use of third-party apps or devices which ask you to sign in to your Google Account using only your username and password.
Please note this deadline does not apply to Google Workspace or Google Cloud Identity customers. The enforcement date for these customers will be announced on the Workspace blog at a later date.
For more information, please continue reading.
Special Note on Apple Device Sign-Ins. Users who have not recently signed into their Google Account using only username and password will be able to only make new sign in attempts using the Google account type starting from February 28, 2022. Existing users may continue to sign into their Google Account using their username and password until May 30, 2022.
-----------------------------------------
Google wants you to use a browser to access email and to store your email on their servers. OAuth 2.0 is very much oriented for use with a browser. I examined implementation without using a browser, but decided that it was far too much work. Outside of OAuth 2.0, there are 2 ways of accessing Gmail. One was to allow the use of "Less Secure Apps", and the other was "2 Factor Authentication". Even though Gmail can only be used with TLS (Transport Layer Security), password guessing is still relatively easy if you allow the user to create that password. So Gmail allows the use of App Password. "An App password is a 16-digit passcode that gives a non-Google app or device permission to access your Google Account". Providing you have a Google account, you can use "2 Factor Authentication" to obtain a token to allow your App to access Gmail. Further information can be found here:
https://support.google.com/accounts/...n-app-password
On a further note, Gmail currently supports versions of TLS that are considered deprecated. I personally consider any versions of TLS that support RSA encryption to be insecure, so I would not be surprised in the future to see Gmail restrict access to TLS 1.3 or better.
J.A. Coutts
Re: Sending Email via Gmail changing for May 30
A couple forum members apparently do have code for using OAuth 2.0, and wqweto's was specifically with an app that connected to a Google service:
https://www.vbforums.com/showthread....6333-OAuth-2-0
Re: Sending Email via Gmail changing for May 30
WELL...setting up a 16-digit passcode ("Generate app password) SEEMS TO WORK (at least TODAY). Tomorrow, when my two programs (one for church and one for family) run (around 3AM) to send me email notifications, I will know for sure. Then, when 31 May comes, I'll see!!!
Thanks for pointing me in the right (I hope) direction.
(From Google:)
Create & use App Passwords
If you use 2-Step-Verification and get a "password incorrect" error when you sign in, you can try to use an App Password.
- Go to your Google Account.
- Select Security.
- Under "Signing in to Google," select App Passwords. You may need to sign in. If you don’t have this option, it might be because:
- 2-Step Verification is not set up for your account.
- 2-Step Verification is only set up for security keys.
- Your account is through work, school, or other organization.
- You turned on Advanced Protection.
- At the bottom, choose Select app and choose the app you using https://www.vbforums.com/images/ieimages/2022/03/1.jpg Select device and choose the device you’re using https://www.vbforums.com/images/ieimages/2022/03/1.jpg Generate.
- Follow the instructions to enter the App Password. The App Password is the 16-character code in the yellow bar on your device.
- Tap Done.
Tip: Most of the time, you’ll only have to enter an App Password once per app or device, so don’t worry about memorizing it.
Re: Sending Email via Gmail changing for May 30
Well, it worked this morning on both of my automatic emailing programs using the 16-digit passcode. Now, just to see if this IS the solution for Less Secure Apps come the end of May.
Re: Sending Email via Gmail changing for May 30
Quote:
Originally Posted by
SamOscarBrown
Tip: Most of the time, you’ll only have to enter an App Password once per app or device, so don’t worry about memorizing it.
You don't have to memorize the 16 character passcode, but you do need to record that value. When I moved my email program to a new computer, it would not work until I activated the passcode on the new machine. Google then sent me an email to a backup account warning me of the attempt.
J.A. Coutts
Re: Sending Email via Gmail changing for May 30
Thx couttsj...yeah, i figured as much as that code is for a specific device. Of course I have the passcode in my vb code, so I can just copy-paste to another device if I ever need...but then, as you warned, I will have to activate it again (I'll learn THAT process if I ever need to do so).
Re: Sending Email via Gmail changing for May 30
App Passwords are *not* per device i.e. you can use it with your google account from a desktop VB6 application and from your mobile phone Mail application for instance.
Not sure if there is any activation mail sent for any previous (old) app passwords being reused, only for new ones. Probably talking about the notification mail when a new app password is being added.
cheers,
</wqw>
Re: Sending Email via Gmail changing for May 30
Quote:
Originally Posted by
wqweto
App Passwords are *not* per device i.e. you can use it with your google account from a desktop VB6 application and from your mobile phone Mail application for instance.
Not sure if there is any activation mail sent for any previous (old) app passwords being reused, only for new ones. Probably talking about the notification mail when a new app password is being added.
cheers,
</wqw>
I don't remember the exact details as I was getting very frustrated at the time, but you are probably correct. I do remember having to enter that 16 byte code manually, and having to dig through my files to find it. It was either that or decode it from the registry.
J.A. Coutts
Re: Sending Email via Gmail changing for May 30
I tried using chilkat Software. Please check examples.
https://www.example-code.com/vb6/gma...cess_token.asp
Re: Sending Email via Gmail changing for May 30
I tried using chilkat Software. Please check examples.
https://www.example-code.com/vb6/gma...cess_token.asp
Re: Sending Email via Gmail changing for May 30
Please do following steps.
In Google Account Activate 2-step verification.
Select App Password in Google Account => Security => Signing to Google.
In Select App Combo Select Other and Name as Windows App & Click Generate it.
Copy Password and use it in place of email password.
It will work.
Re: Sending Email via Gmail changing for May 30
Quote:
Originally Posted by
microbrain
Please do following steps.
In Google Account Activate 2-step verification.
Select App Password in Google Account => Security => Signing to Google.
In Select App Combo Select Other and Name as Windows App & Click Generate it.
Copy Password and use it in place of email password.
It will work.
So buying Chilkat licenses is optional then?
For an instance I though Google started force selling 3-rd party licenses on 30-th of May which got me worried a bit. . .
Re: Sending Email via Gmail changing for May 30
I just had my customers change up to use their ISP's email and got everybody off Gmail.
Re: Sending Email via Gmail changing for May 30
I did what coutsjj posted (but I did it when Google first 'warned' of it---see Posts #11 & 12), and, knock on wood, my program using gMail has been working daily (even after 30 May)