Skyla Posted December 13, 2022 Share Posted December 13, 2022 (edited) Bug Report - #VQF-804057 == Description ==Mail import has been working for years. Yesterday, I had to update the Client Secret for the Google OAuth2 credentials and I noticed the "Email Address" field was blank which I thought was odd. I was able to fill in the Email Address and reconnect and test the config successfully. I thought everything was OK and "Saved Changes".Shortly after saving, I started getting failed POP3 connection alerts. Error below.Error: cannot connect to host ; error = stream_socket_client(): Unable to connect to tcp://: (Failed to parse address ":") (errno = 0 )When I went back to check, I noticed the Email address is blank again. If I "Test Configuration" as-is, it fails as well with the error below. Which is expected since no emails are tied to it. When I fill the email in and test again, the test works again. The email doesn't save.The Mail Import test failed: Oauth2 auth failed, BAD Invalid SASL argument. e16mb7724676qvq: {"status":"400","schemes":"Bearer","scope":"https:\/\/mail.google.com\/"}Something seems wrong with the Email Address field causing it to not save.I tested on the latest Edge, Chrome and Firefox.== Steps to Reproduce == Go to WHMCS Admin Go to Support Ticket Departments in System Settings Access any Departments that have OAuth2 authentication and check "Email Address" Field will be blank. Will work if filled in and connecting or testing the OAuth credentials. Field "Saves" blank even if filled in. == Expected Result ==The Email Address should already be filled in (if OAuth2 is already set up). The Email Address should save instead of going blank again.This is specifically for the "Mail Importing Configuration" in Support Departments.== PHP Version ==8.1.12 Edited December 13, 2022 by Skyla 0 Quote Link to comment Share on other sites More sharing options...
Balram Posted March 12, 2023 Share Posted March 12, 2023 Any fix for this? 0 Quote Link to comment Share on other sites More sharing options...
Skyla Posted March 14, 2023 Author Share Posted March 14, 2023 No fix yet. The workaround is to revert to using standard password auth instead of using OAuth. For Workspace/Gmail, you likely need to use an App Password if you use 2FA/MFA 0 Quote Link to comment Share on other sites More sharing options...
Skyla Posted March 24, 2023 Author Share Posted March 24, 2023 This is now fixed in 8.7 CORE-18390 - Correct saving of new Google OAuth2 POP support department email addressesAlso known as: CORE-18352 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.