- Comcast imap settings for outlook 2013 Patch#
- Comcast imap settings for outlook 2013 Offline#
- Comcast imap settings for outlook 2013 download#
I was just double checking about the dialog boxes being used. It’s not ideal, but most workarounds are not and it’s better than no encryption while waiting for MS to issue a patch.:rolleyes: My guess is that he did a workaround to allow a version of SSL rather than TLS. I then had to change the SMTP encoding from TLS to SSL. This time I could specify POP3 connecting to port 995 using SSL. He made some adjustments and asked me to try again. I shared that info with the email server admin. Back in Outlook 2013, only SSL could be specified for POP3 only SMTP had the option for TLS encoding. The clue, for me was when I loaded Thunderbird where I could specify TLS for POP3 and it connected without error. This didn’t present a problem for browsers and Https webmail was still possible. Soon afterward, most servers disabled SSL 3.0, and moved to TLS.
It took a lot of persistence, but I can finally connect to Pop2 using encryption.:D MS posted a security bulletin about a security flaw found in SSL 3.0.
Comcast imap settings for outlook 2013 Offline#
I suspect that they briefly took that connection offline a couple of weeks ago, as I couldn’t connect for a few hours, but it later resumed. It, too, works when POP3 is configured as SSL connecting to port 995. I’m not sure what 1&1 (in your link) or other large email providers have done as a workaround that allows the SSL setting for incoming mail.
Comcast imap settings for outlook 2013 Patch#
I assume that is why there has not been a patch for Outlook 2013 yet. It is only POP3 or IMAP that shows the server does not support the selected encryption method.Ī MS tech tried to assure people in the MS Community Forum that it really wasn’t a security flaw. I have continued to be able to connect to the secure port for SMTP. Setting up Thunderbird to use TLS for POP3 connects properly. The problem seems to be that Outlook 2013 only uses SSL for incoming mail. TLS is active on both my incoming and outgoing mail servers. That wasn’t a problem as TLS was available (or installed on most servers) and could be used by browsers. SSL was removed from most server installations and disabled in IE11. Microsoft issued a security advisory 3009008 after discovery of the Poodle bug affecting SSL 3.0. I’ve been doing more research on the issue.
My webhost admin seems stumped, so I would like to point him in the right direction. Googling the error turns up many examples of the same issue, but most are old and resolved by the email server admin. I’ve also temporarily disabled both my anti-malware and firewall. In addition to making sure that Outlook is configured for the mail account correctly, I created a new profile, having it create a new data file. Within a few hours, I could once again connect securely.
Comcast imap settings for outlook 2013 download#
While travelling late last month, I had the identical error trying to download mail from Comcast. The cPanel recommended settings are the same that I had used successfully until sometime last month when I would get an error that the encryption method was not supported by the server I’m trying to connect to. The issue is specifically with the mail servers for my website. Oddly, my wife’s system set up nearly identical to mine, except for using Outlook 2007, can use the same settings as me and successfully connects to the secure ports. So far neither an Outlook tech from MS remotely controlling my computer nor the email server admin has been able to get my desktop Outlook 2013 (365 Home) to connect to either the secure IMAP port 993 or secure POP3 port 995.
0 kommentar(er)
