You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Unable to connect to imap store with imap.gmail.com host. it always throws java.lang.NumberFormatException: For input string: "CAPABILITY" , when try to connect imap store.
To Reproduce
execute this peice of code
host = imap.gmail.com, email = your gmail where app password is created, appPassword = app password created in gmail
Properties properties = new Properties();
properties.put("mail.imap.host", host);
properties.put("mail.imap.port", "993");
properties.put("mail.imap.ssl.enable", "true");
properties.put("mail.debug", "true");
properties.put("mail.imap.enablecapability", "false");
Session emailSession = Session.getDefaultInstance(properties);
Store store = emailSession.getStore("imap");
store.connect(host, email, appPassword);
Expected behavior
should successfully connect with store and return store instance to perform furthur action like read Inbox etc
Screenshots
Desktop (please complete the following information):
OS: Window 11
Browser: Chrome
Version Version 131.0.6778.205
Smartphone (please complete the following information):
N/A
Mail server:
Protocol being used: imap
Vendor/product: [e.g. Microsoft Exchange]
Mail service URL: imap.gmail.com
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
Unable to connect to imap store with imap.gmail.com host. it always throws java.lang.NumberFormatException: For input string: "CAPABILITY" , when try to connect imap store.
To Reproduce
host = imap.gmail.com, email = your gmail where app password is created, appPassword = app password created in gmail
Expected behavior
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
N/A
Mail server:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: