Support IMAP ID (RFC 2971) for NetEase 163 IMAP login

[tigerymh-lab]

Dear team,

Please kinly help to check this requirement.

Thanks.

!

Summary

NetEase 163 IMAP login is rejected unless the client sends IMAP ID information.
At the moment, Himalaya appears unable to complete login successfully with imap.163.com, even when the server, port, TLS, and authorization code are correct.

Environment

• Himalaya version: v1.2.0
• Provider: NetEase 163 (@163.com)
• IMAP server: imap.163.com
• IMAP port: 993
• Encryption: SSL/TLS
• Authentication: authorization code / app password

What happens

Running:

himalaya envelope list -a "<account>"
returns:

textCopyCopied!
unexpected NO response: SELECT Unsafe Login. Please contact kefu@188.com for help
Debug notes
The connection and TLS negotiation succeed, and the password command is executed correctly.
The failure happens when accessing the mailbox after login.

Provider response
NetEase support explained that their IMAP service requires the client to send IMAP ID information when connecting.
If the client does not provide IMAP ID metadata, the server may reject access with:

textCopyCopied!
Unsafe Login. Please contact kefu@188.com for help
They said common clients such as Outlook, Foxmail, and NetEase Mail Master do not have this issue because they send IMAP ID.

Request
Could Himalaya support sending IMAP ID metadata (RFC 2971), for example fields like:

name
version
vendor
support-email
A configurable account-level option would be especially useful for providers like NetEase 163.

Reference
RFC 2971: https://www.ietf.org/rfc/rfc2971.txt
CopyCopied!

[HayashiZF]

在config.toml 中添加 backend.extensions.id.send-after-auth = true，然后我就可以用163了
Add backend.extensions.id.send-after-auth = true to config.toml