Hi @SokiGuo-MSFT
I appreciate your intention to help, but there must have been some misunderstandings.
You may reread the information provided so far carefully and take note of these further explanations:
Unfortunately, there is no official Microsoft documentation on how to set up IMAP for T-online accounts.
Nobody has asked about this here anyway so far, but here it is: https://support.microsoft.com/en-us/office/server-settings-you-ll-need-from-your-email-provider-c82de912-adcc-4787-8283-45a1161f3cc3
The official documentation you provided above is about the port settings for outlook.com account configured as IMAP.
As mentioned neither Outlook.com nor Microsoft 365 accounts are related to the issue we are talking about here; even though Microsoft also fails to support TLS 1.3 there with their IMAPS server as already mentioned: https://testtls.com/outlook.office365.com/993
Since our testing environment is limited.
I'm sorry to hear that basic tools like Packet Sniffer are not provided to help you with connection issues related to TLS encryption.
Presumably the folks from https://support.microsoft.com/en-us/topic/outlook-imap-or-pop-server-unexpectedly-terminated-the-connection-and-the-server-was-interrupted-39fb3fde-7abe-4fff-a98d-9a7872b74ab5 shall jump in because what they have written isn't true (anymore): "Our testing found that Windows 11 TLS 1.3 should be working fine with Outlook."
...we are not able to configure your T-online account...
Because the problem is related to a the (lower) TLS protocol layer, this is not necessary.
We recommend that you contact your email provider for more professional advice.
Because it has already been proven that Outlook is the issue email providers cannot help. They are victims too, because - just like nowadays with TLS 1.0 - sometime they'll again have to deal with software not updated protocol support.