14 replies

Leave a reply

Your email address will not be published. Required fields are marked *

  1. where do I find the generater to make the password?
    I was hacked and now I can’t get into my g-mail with out doing a account restore.
    all I need is the program to make the password.
    Thanks
    Bon

  2. Do you know if there’s a limit as to how many app passwords can be created for an email account? I don’t see anything in Google’s documentation.

  3. brilliant! The authorization step at the end is the bit I was missing, just followed the link and it now works. Thank you! Very happy!

  4. I can say this DOES work. Do not use the spaces generated in password. These spaces are iD10 spaces (sorry) for error proof entering.

    BUT!!

    My issue is to differentiate 3 separate app passwords for 3 separate apps for the same gmail email account that all land to the said account looking as if it came from the same entity…..What I Need Is an App Specific AppPassword to differentiate its’ origin.

    Can you please help with that?

  5. On some rare occasions, I want my Python app on a Raspberry Pi to send me a message using my GMail account as the SMTP service. This works currently, except that Google automatically disables the app’s access to GMail after a certain time. If I do not “catch” this event, and manually restore the app’s permissions, then I do not receive these rare but important messages from my Raspberry Pi.

    Google has implied that configuring one’s account to use 2FA will also enable one to generate an app password. Google further implies that this app password will avoid the problem I describe in the first paragraph, but this is a rather vague assurance because it’s stated here that the app will get “restricted access“. Google has also been known to terminate services and features for various reasons. All of this uncertainty leads me to wonder if I’m merely an unknowing participant in an experiment, or if this 2FA and app password will solve my current problem.

    And so I have some questions:

    Is the use case I described in the first paragraph one that would be allowed under Google’s definition of “restricted access“?
    Are the 2FA and “app password” services ones that are likely to be somewhat durable elements in Google’s efforts toward security?
    If I change my GMail account to use 2FA, and subsequently decide that it doesn’t suit me, can I revert to the current userid & password scheme I have now?

    Thanks for your time.

    1. Hi Séamus,

      I assume you have you done this step? Allow less secure apps to access your Gmail account.

      I’m not surprised if Google is blocking the RasPi periodically if you are using your main Google Account password to authorise SMTP. Google login security isn’t as lax as it once was.

      You should try setting up 2FA and then give your RaspPi an app password, which should relax Google’s login security for the RaspPi. Personally I use Postfix to access Gmail SMTP without issues: How to configure Postfix to use Gmail SMTP on Ubuntu

      The whole point of an app password is that it restricts access to your Google account so if your app password is ever compromised, your entire Google account cannot be hijacked.

      And, yes, you can disable 2Fa and revert back to the old method if needed.

  6. then app password created ???. Even When i login using email and app generated password, still got incorrect password. Where should i use it ?? or should i change password with it??. I didnt understand after this processs