• Resolved korinthe

    (@korinthe)


    Hi, Postie worked perfectly with GMail (and GoDaddy hosting) using IMAP-SSL from 9/16/23 – 10/24/25 or 10/25/25. Then it either stopped being invoked by cron, or was invoked and failed to alert via “Notify on Error” address.
    At any rate I discovered the problem today and have been attempting to debug via the manual buttons, taking cron out of the equation for starters.
    Regardless of whether I am using IMAP-SSL vs POP-SSL, or the account’s “real” password vs an app password, I keep getting “Permission denied”.

    If it helps, this is a Google Workspace account, and I admin the domain. I also tried it with 2FA disabled, no use.

    I found the following in the Google Workspace Admin help (https://support.google.com/a/answer/6260879?hl=en&ref_topic=10021546&sjid=6332810799197049535-NC):

    Starting May 1, 2025, Google Workspace accounts no longer support less secure apps, third-party apps, or devices that ask you to sign in to your Google Account with your username and password. You must use OAuth to let these apps and devices access your account. Third-party email apps that are no longer supported include Microsoft Outlook and the mail app on iOS and macOS. For detailed instructions and information, visit Transition from less secure apps to OAuth. For the latest dates, visit Google Workspace Updates.

    So… until we have OAuth in Postie (?) do you know of any way to test the “app password” works from outside of Postie/GoDaddy?

    I did take the spaces out of it, since Google says it’s a 16-char password.

Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.