C
Cparas101
Guest
I have read through many articles about the issue with Outlook opening up a certificate mismatch warning. I have found reg key resolutions for Outlook 2010 and 2013 but for Outlook 2016, nothing besides Autodiscover A record, cname resolution.
I have a Comcast account, within Outlook I am setting it up the account as IMAP,
Incoming mail server: imap.comcast.net
Outgoing mail server: smtp.comcast.net
Use authentication, use same as incoming
Incoming mail: SSL: 993
Outgoing mail:TLS:465, 587 does not work?
Only on the users computer do I receive the certificate mismatch warring. The computer is running Windows 10 Pro. I can setup the account on same type of computer, Windows 10 Pro, Office 2016 installed from same 365 account using the same settings within Outlook without the certificate warring?
Any suggestions other than Comcast needs to change their A record?
Continue reading...
I have a Comcast account, within Outlook I am setting it up the account as IMAP,
Incoming mail server: imap.comcast.net
Outgoing mail server: smtp.comcast.net
Use authentication, use same as incoming
Incoming mail: SSL: 993
Outgoing mail:TLS:465, 587 does not work?
Only on the users computer do I receive the certificate mismatch warring. The computer is running Windows 10 Pro. I can setup the account on same type of computer, Windows 10 Pro, Office 2016 installed from same 365 account using the same settings within Outlook without the certificate warring?
Any suggestions other than Comcast needs to change their A record?
Continue reading...