![]() ![]() You are not allowed to use Gmail to send email in violation of the CAN-SPAM Act or other anti-spam laws to send unauthorized email via open, third-party servers or to distribute the email addresses of any person without their consent. Spam and Bulk Mailĭon’t use Gmail to distribute spam or unsolicited commercial mail. We may take action on inactive accounts, which may include deleting your messages from the product. Activity includes accessing the product or its content at least every 2 years. If your account is disabled, and you believe it was a mistake, please follow the instructions on this page. Google may disable accounts that are found to be in violation of our policies. Make sure to read the policies below to understand how we define abusive behavior. If you believe an account has violated our Program Policies, there are multiple ways to report it: Read more about storage quotas here.īe sure to check back from time to time, as these policies may change. We may also delete content from your account if you fail to reduce your storage or fail to obtain sufficient additional storage. For example, we may prohibit the sending or receiving of messages if you exceed your storage quota. We may take action on accounts that go above storage quota limits. After we are notified of a potential policy violation, we may review the content and take action, including limiting or terminating a user’s access to Google products. We need to curb abuses that threaten our ability to provide these services, and we ask that everyone abide by the policies below to help us achieve this goal. Your administrator may be able to provide more information. If you’re using an account through work, school, or another organization, terms may apply based on your organization’s agreement with Google or other policies. If you use Gmail with a consumer (e.g., account, please also refer to Google’s Terms of Service for more information. The policies play an important role in maintaining a positive experience for everyone using Gmail. Java is a registered trademark of Oracle and/or its affiliates.The Program Policies below apply to Gmail. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |