邮件监听异常
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 164
- PR merge metrics
- No merged PRs in 30d
Description
Exception in thread "Timer-0" org.dromara.email.jakarta.comm.errors.MailException: jakarta.mail.MessagingException: A3 NO SELECT Unsafe Login. Please contact kefu@188.com for help;
nested exception is:
org.eclipse.angus.mail.iap.CommandFailedException: A3 NO SELECT Unsafe Login. Please contact kefu@188.com for help
at org.dromara.email.jakarta.core.service.MonitorService.startListening(MonitorService.java:98)
at org.dromara.email.jakarta.core.service.MonitorService.access$000(MonitorService.java:33)
at org.dromara.email.jakarta.core.service.MonitorService$1.run(MonitorService.java:122)
at java.base/java.util.TimerThread.mainLoop(Timer.java:566)
at java.base/java.util.TimerThread.run(Timer.java:516)
Caused by: jakarta.mail.MessagingException: A3 NO SELECT Unsafe Login. Please contact kefu@188.com for help;
nested exception is:
org.eclipse.angus.mail.iap.CommandFailedException: A3 NO SELECT Unsafe Login. Please contact kefu@188.com for help
at org.eclipse.angus.mail.imap.IMAPFolder.open(IMAPFolder.java:1083)
at org.eclipse.angus.mail.imap.IMAPFolder.open(IMAPFolder.java:1011)
at org.dromara.email.jakarta.core.service.MonitorService.startListening(MonitorService.java:58)
... 4 more
Caused by: org.eclipse.angus.mail.iap.CommandFailedException: A3 NO SELECT Unsafe Login. Please contact kefu@188.com for help
at org.eclipse.angus.mail.iap.Protocol.handleResult(Protocol.java:420)
at org.eclipse.angus.mail.imap.protocol.IMAPProtocol.select(IMAPProtocol.java:1252)
at org.eclipse.angus.mail.imap.IMAPFolder.open(IMAPFolder.java:1068)
... 6 more
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with org.dromara.email.jakarta.core.service.MonitorService, especially startListening at lines 58, 98, and 122, and trace the IMAP folder-opening path shown in the stack trace. Reproduce the listener with the affected mail account and determine the expected handling for the provider's “Unsafe Login” response; the issue is done when the intended monitoring behavior is verified without this failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100