<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>google-importing on</title><link>https://docs.whmcs.com/9-1/tags/google-importing/</link><description>Recent content in google-importing on</description><generator>Hugo -- gohugo.io</generator><atom:link href="https://docs.whmcs.com/9-1/tags/google-importing/index.xml" rel="self" type="application/rss+xml"/><item><title>Invalid SASL Argument Errors</title><link>https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-the-support-system/ticket-replies/invalid-sasl-argument-errors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-the-support-system/ticket-replies/invalid-sasl-argument-errors/</guid><description>Covers &amp;ldquo;invalid SASL argument&amp;rdquo; and OAuth2 email importing errors caused by missing Google OAuth2 authentication information, with a MySQL workaround query to update the department&amp;rsquo;s login value.</description></item><item><title>POP3 [AUTH] Errors</title><link>https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-the-support-system/ticket-replies/pop3-auth-errors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.whmcs.com/9-1/troubleshooting/troubleshoot-the-support-system/ticket-replies/pop3-auth-errors/</guid><description>Documents &amp;ldquo;[AUTH] Username and password not accepted&amp;rdquo; caused by Gmail no longer supporting basic username and password IMAP authentication, with the fix of switching the department&amp;rsquo;s email importing configuration to OAuth2.</description></item></channel></rss>