Looks like that Outlook is detecting a mismatch between the server name you’ve configured in your POP3 account settings and the names listed in the security certificate provided by your email provider. In simple terms, the certificate’s subject (or one of its Subject Alternative Names) does not match the domain name Outlook is using to connect.
Even though the certificate appears valid (issued by Sectigo RSA Domain Validation Secure Server CA), the check on the identifier name is failing.
Some troubleshooting you can do;
- Server Name Mismatch: The POP3 server name configured in Outlook might not match the common name (CN) or Subject Alternative Name (SAN) on the certificate. For example, if the certificate is issued to mail.sos4net.com but your account is connecting to pop.sos4net.com, Outlook will flag it as a mismatch.
- Changed DNS Settings or Certificate Renewal: It’s possible that your email provider renewed the certificate or updated their DNS records. Even a subtle change (for example, replacing a “www” prefix, or switching between “pop” and “mail”) can trigger the error.
- Different Behavior Between Clients: Mobile clients (iOS Mail, for instance) sometimes handle certificate mismatches more leniently or might have cached prior connections differently. Outlook for Windows, especially in the “Classic Outlook” mode, tends to enforce stricter security validations.
- Cached Settings or DNS Issues: Occasionally, cached DNS entries or Outlook settings can cause an outdated server name to be used, even if the provider’s certificate has been updated.
😊 If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!