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.

What is the smtp server for gmail