Announcement

Collapse
No announcement yet.

WARNING, Google/Gmail breaks IMAP/POP3, Jan 2025 Could break KDM automation

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • WARNING, Google/Gmail breaks IMAP/POP3, Jan 2025 Could break KDM automation

    Just wanted to heads up everyone.
    Google/Gmail, application passwords will no longer work from end Jan 2025.
    OAuth will be the only supported login mechanism after that date.


    If you have a KDM automation system that scans Email accounts, they are typically IMAP/POP3 based.
    If you use Gmail, you must take action before end Jan.

  • #2
    TheScream.jpg
    Oh Noooooo!
    Last January many of us were dealing with the dreaded
    certificate kerfuffle. . . now this! What next?

    Comment


    • #3
      Assuming Google doesn't change thing again (which may not be a safe assumption) you can probably continue to use whatever you use to fetch gmail messages by setting up an "app password" for gmail.

      Description here: https://support.google.com/mail/answer/185833?hl=en

      A lot of stuff (standard mail clients, fetchmail, etc.) doesn't support oauth2 so if you can do this nothing will change about the process or procedure. Just the actual password you'll have to use to login.

      I guess is an attempt to to force everyone to use google's own gmail client or the gmail webpage and stamp out third party access so I don't know how long this app password procedure will work but it's certainly worth a try.

      Comment


      • #4
        The quick fix without "too" much headache is to turn on auto-forwarding on your gmail account, and forward to a mail host that supports IMAP/POP still. At least then you don't have to update the distributors in a jam. (But you still have to update your local processes).

        KB Article on Forwarding:
        https://support.google.com/mail/answer/10957?hl=en

        Comment


        • #5

          Frank.. No. Google says end Jan 2025. App passwords will no longer work period.

          Yes, I started by forwarding to another server I set up myself. In my little data centre, I kicked up a VPS specifically to run a SMTP server specifically for being a messaging service for KDMs.
          Used a minimum, install Ubuntu LTS. add Docker then...
          Docker compose file for mailcow-dockerized
          Have a nice GUI. Worked out of the box. Create accounts easy. Have a Web client if you want to login and check the Mail for the mailbox you created, i.e. for debugging and testing.

          Comment


          • #6
            Fron day one after we went digital, we used two completely separate email accounts for KDMs. All KDM service companies send our KDMs to both accounts. Just in case either one of these companies would have or cause issues.

            Comment

            Working...
            X