You can also transfer files using the addon domain’s unique login information. If your FTP program does not ask for a destination folder/file path, you will need to navigate to the addon domain’s folder through the FTP program before you start transferring files. In the above, replace “” and “” with the actual domain names. Host/Server Address: (without the “Port: 21 (you may not be asked for the port number – it depends on the FTP program) Your FTP login information would then be: To FTP files to an addon domain, use the same information you would use for your primary domain name, with one change: instead of the destination folder/file path being listed as /public_html, it should be /public_html/ ( replacing “” with the actual domain name). You may FTP files to an addon domain in two ways: SSL Certificates Earn the trust of your website visitors.Automated Website Backup Protect yourself and your website with backups.SiteLock Inspire visitor confidence and be malware free.Protection Power Secure and proactively monitor your website.Microsoft 365 Microsoft’s tried and true Office 365 solution.Google Workspace Power your email by Gmail and Google Drive apps.Business Email Professional email on your domain name.Overview Compare all HostPapa email plans.Do-It-For-Me Let us help you get your business online.Website Builder Start fresh or choose from our professional templates.PapaCare+ Never worry about site related problems.Reseller Hosting Bill your clients and use our infrastructure.Managed WordPress Hosting WordPress on steroids, worldwide.Optimized WordPress Hosting Specifically optimized for WordPress.Web Hosting Standard cPanel Web Hosting.Java is a registered trademark of Oracle and/or its affiliates. For details, see the Google Developers Site Policies. The Libraries and Samples page provides code samples in a variety of popular languages using the SASL XOAUTH2 mechanism with either IMAP or SMTP.Įxcept as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. In addition to the SASL XOAUTH2 protocol documentation, you may also want to read Using OAuth 2.0 to Access Google APIs for further information on implementing an OAuth 2.0 client. As long as these libraries support the Simple Authentication and Security Layer (SASL), they should be compatible with the SASL XOAUTH2 mechanism supported by Gmail. Libraries and SamplesĪccessing mail using IMAP or POP and sending mail using SMTP is often done using existing IMAP and SMTP libraries for convenience. If using OAuth, make sure that the access token used is valid (if you try to use an access token older than 1 hour, it might be invalid). After that, the client can reconnect, authenticate again, and continue. When the time elapses and the session expires, Gmail closes the connection with a message saying that the session expired. A session in this context is one continuous TCP connection. If the session was authenticated using OAuth credentials, it's limited to about the validity period of the access token used (usually 1 hour). Gmail IMAP sessions are limited to about 24 hours. Gmail POP sessions are limited to about 7 days. If your client begins with plain text, before issuing the STARTTLS command, use port 465 (for SSL), or port 587 (for TLS). The outgoing SMTP server,, supports TLS. Incoming connections to the IMAP server at :993 and the POP server at :995 require SSL. The SASL XOAUTH2 protocol documentation describes the SASL XOAUTH2 mechanism in great detail, and libraries and samples which have implemented the protocol are available. The SASL XOAUTH2 mechanism enables clients to provide OAuth 2.0 credentials for authentication. IMAP, POP, and SMTP use the standard Simple Authentication and Security Layer (SASL), using the built-in the native IMAP AUTHENTICATE, POP AUTH, and SMTP AUTH commands, to authenticate users. The Gmail IMAP, POP, and SMTP servers have been extended to support authorization via the industry-standard OAuth 2.0 protocol. For non-Gmail clients, Gmail supports the standard IMAP, POP, and SMTP protocols.