IMAP Google: Nuove Regole

The Google (Gmail) IMAP server in 2025 is still imap.gmail.com using port 993 with SSL, but there have been significant changes to authentication: as of early 2025, you must use OAuth 2.0—application passwords and basic authentication methods (username/password combos) are no longer supported for IMAP and POP access ^{[2] [3] [6]}. This change impacts all apps or devices that connect to Gmail via IMAP, including those used for automation, third-party email apps, and older clients.

Key details for Google IMAP in 2025:

• IMAP server: imap.gmail.com
• Port: 993
• Security: SSL required
• Authentication: OAuth 2.0 (application passwords are no longer accepted after January 2025) ^{[2] [3]}

Important authentication change:
From the end of January 2025, Google/Gmail requires OAuth 2.0 for IMAP access—older methods like application-specific passwords have been discontinued ^{[2] [3]}. Any automation or email client setup using basic username/password authentication will stop working unless migrated to OAuth.

Alternative for developers:
Google increasingly recommends the Gmail API (which uses RESTful access and OAuth) for more robust integrations, as it offers more granular control and better security than standard IMAP ^[7].

Settings like IMAP server address, port, and SSL have not changed, but updating the authentication method is now a requirement ^[6].

If you manage a Google Workspace domain, enabling IMAP for users still follows the usual process, but all access must comply with the new authentication requirements ^[1].

If you are attempting to connect an existing client, make sure it supports OAuth 2.0 for Gmail IMAP; otherwise, it will no longer work with Google’s servers in 2025 ^{[2] [3] [6]}.