Open MilkTeaCat52 opened 1 month ago
bkaankose
commented
2 weeks ago ID extension was supported for Wino since 1.7.1, but identification is done pre-authentication. Looks like some servers require this before authentication and some after.
This is fixed by trying identification pre-post auth in the code, but the version is not released yet. 1.7.4 will have this fix included.
chenseanxy
commented
2 weeks ago This might not be the post-auth ID thing. 126/163 supports ID pre-auth.
IMO this is more likely than not some sort of acccount ban. On the testing account I gave to @bkaankose it's still working, but not on my personal account.
More likely than not it's based on the specific app-password you use to login to IMAP, if that client gets logged with too much traffic they'll ban the specific app-password used on that account. Recreating a new password solves this issue for a while, until that gets banned again.
I'll ask the customer support for more help on the issue, to see if there's really any sort of ban, and if we can do anything about it.
Describe the bug After the @163.com email is added for the first time via IMAP, synchronization completes successfully. Subsequently, synchronization fails on every attempt. The error message is: The IMAP server replied to the 'SELECT' command with a 'NO' response: SELECT Unsafe Login. Please contact kefu@188.com for help
Emails can be sent as normal.
Expected behavior Synchronization of emails from the NetEase IMAP server.
Screenshots
Additional context From another GitHub repo, the reason seems to be: "The IMAP server at imap.163.com implemented the IMAP ID extension. To successfully authenticate, the IMAP client must send client ID." https://github.com/OfflineIMAP/offlineimap/issues/696