I found this plus.net help article that provide server name and port information but does specifically state whether the authentication username should be in the form of just the username part of your email address or the entire email address (eg: username@domain.com) so I would try both.
https://www.plus.net/help/email-guides/how-to-set-up-plusnet-email/
I assume you have reentered the password to insure it is correct.
There is an internet session logging function that can help with troubleshooting. It can be enabled by a check box at the bottom of the General tab in Tools > Internet options. The log file will be created in a subdirectory of the mailbox directory. That subdirectory is named TCPLogs. The log files will have an extension the identifies the protocol that was logged but they are plain text files so can be viewed with a text editor. Do not post an entire log, it will contain your login credentials, sometimes in plain text, sometimes encrypted. If you see them in plain text then you can remove them and post the log. I you don't see them, don't post the log because they are there in an easily decryptable form. We can tell you how to identify and remove them if needed so that you can post the log but often you can identify the specific log entries that identify the failure and you can advise us based on what you see.
I found this plus.net help article that provide server name and port information but does specifically state whether the authentication username should be in the form of just the username part of your email address or the entire email address (eg: username@domain.com) so I would try both.
https://www.plus.net/help/email-guides/how-to-set-up-plusnet-email/
I assume you have reentered the password to insure it is correct.
There is an internet session logging function that can help with troubleshooting. It can be enabled by a check box at the bottom of the General tab in Tools > Internet options. The log file will be created in a subdirectory of the mailbox directory. That subdirectory is named TCPLogs. The log files will have an extension the identifies the protocol that was logged but they are plain text files so can be viewed with a text editor. Do not post an entire log, it will contain your login credentials, sometimes in plain text, sometimes encrypted. If you see them in plain text then you can remove them and post the log. I you don't see them, don't post the log because they are there in an easily decryptable form. We can tell you how to identify and remove them if needed so that you can post the log but often you can identify the specific log entries that identify the failure and you can advise us based on what you see.
