Server issue compatibility: MailKit 4.16.0 connect imap.sohu.com:993 has exception for CAPABILITIES
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.9k
- Forks
- 866
- PR merge metrics
- No merged PRs in 30d
Description
Host: imap.sohu.com
Port: 993
Log:
Connected to imaps://imap.sohu.com:993/
S: * OK IMAP4 ready
C: C00000000 CAPABILITY
S: * CAPABILITY IMAP4 IMAP4rev1 UIDPLUS IDLE AUTH=PLAIN
S: C00000000 OK completed
C: C00000001 AUTHENTICATE PLAIN
S: +
C: ********
S: C00000001 OK LOGIN completed
C: C00000002 CAPABILITY
S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=LOGIN IDLE MOVE NAMESPACE
S: C00000002 OK CAPABILITY completed
C: C00000003 NAMESPACE
S: * CAPABILITY (("" "/")) NIL NIL
Exception: Syntax error in CAPABILITIES. Unexpected token: '('
Actually it probably a server setting issue with NAMESPACE wrongly set to CAPABILITY. However, I can not escape CAPABILITY exception when I try to connect IMAP server. And its related SMTP server don't have this issue. (smtp.sohu.com:465)
I can use other email apps like Outlook to access their IMAP/SMTP server without any issue. So I hope MailKit can add some compatibility for the Server configuration problem so that user can continue to use MailKit to connect email server and operate it.
Thank you, Jeffrey
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the connection to imap.sohu.com:993 using the logged CAPABILITY and NAMESPACE exchange. Start by tracing how MailKit handles the NAMESPACE response, then verify that the malformed server response no longer raises the CAPABILITIES syntax exception and that normal IMAP operations remain usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100