Closed Novgor closed 2 months ago
I'm afraid the response is still the same: this is nothing to do with the proxy. If the switch to a production client hasn't resolved this, you may need to go down the verification route as suggested in your screenshot ($15,000 - $75,000, I believe).
Alternatively, as recommended previously, you can also try one of the available ID/secret pairs from an open source client that has already been verified.
Hello again. Continuation of the case #273 I start the proxy with keys first:
I go through the initial authorization (I go to the provided URL and enter the code in the command line), and smtp and pop3 work. And I continue to work as a proxy without the --external-auth key The configuration looks like this, I do not make any more changes:
A little less than an hour later, the letters stop coming. There is an error in the logs:
More detailed log with the beginning of the error:
I switched the settings in production to google cloud console. But the access token is still given for 1 hour and does not update. I have no idea why this happens(