TLS

4 Topics

I fixed my Outlook email problem after Cox "maintenance"
Hi all, Like all (?) Outlook users, I lost the ability to receive mail a week ago (I could still send). I use Windows 10 Pro, version 1903 (OS build 18362.746). I am using Outlook Version 1911 (build 12228.20332). I fixed my connection issue by disabling the use of TLS 1.0 by Windows 10.I suspect the "maintenance" was to require TLS 1.2 connections. Our Outlook clients are trying to connect using TLS 1.0 and get rejected. Here's how I did it. The first step may not be required -- I think it was the second step that was definitive. NOTE: These directions are essentially the same as those here:https://windowsreport.com/how-to-disable-tls-1-0/ 1. Disable TLS 1.0 in Internet Settings Press Windows Key + S [This will bring up Search] Type "internet options" into search bar The Internet Properties window pops up Select the "Advanced" tab Scroll down to the bottom, the "Security" section. Uncheck "Use TLS 1.0" Note: I also unchecked TLS 1.1, and I checked Use TLS 1.3 (experimental). You may not need to do that. 2. Edit the Registry to Disable TLS 1.0 Press Windows Key + R [this brings up the "Run" window] type "regedit" in Run to run the registry editor Then, in the left-hand tree view, open up this key path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols I couldn't see TLS 1.0 and Client subkeys went I arrived at the end of the above key path, so I had to create them. To create them: right-click on Protocols and select New > Key then enter "TLS 1.0" as the key title Next, right click on the TLS 1.0 key you just created, and select New > Key again. Enter "Client" as the title. Then, select the Client key, and in in the empty-space to the right of it, right-click and select New > DWORD (32-bit) Value Enter "Enabled" as the new DWORD's title The default value for this new Enabled DWORD is 0 (zero), which disables TLS 1.0. Finally, restart Windows (reboot). My Outlook IMAP Settings for Cox The above procedure should have restored your prior configuration to a working state. If it's not, here are is my working Outlook configuration. Recall that I am using Windows 10, with OutlookVersion 1911 (build 12228.20332) as part of Office 365. Note that I use IMAP and not POP. It Outlook, select the File menu In the Account Information screen, press the "Account Settings" button, then select "Server Settings" The IMAP Account Settings -- Incoming mail -- window appears: Now press the "Outgoing mail" link in this window. Now the IMAP settings for outgoing mail appears: Good Luck & Merry Christmas!
blackeneth
5 years ago Place Internet
3.4KViews
1like
0Comments
4.3.3 TLS not available
Suddenly my IMAP account for an offsite server is returning this message when I send email. It appears that the mail is going but I fear that it is not secure (SSL) I have SSL set for this outgoing account and I'm using the Cox SMTP server - smtp.cox.net and port 587 outgoing.
Michael2020
10 years ago Place Archives
2.8KViews
0likes
2Comments
When is StartTLS going to get fixed????
So, I complained about this a couple of years ago that the TLS server was not properly set up. Pretty much gave up seeing it resolved. Then a few weeks after the Snowden leaks I noticed it was working well. Now after a imap issue a few days ago followed by a pop3 issue the next day it appears StartTLS is not working. That is unacceptable. Anyone else want to test Cox's servers on cox.com, cox.net or ww2.cox.com give it a shot. Test your email too. https://www.ssllabs.com/ssltest/index.html https://starttls.info/ https://www.checktls.com/perl/TestSender.pl Feeling secure? Love Cox's support for RC4 ciphers too (sarcasm). But at least you dropped the flawed DHE ciphers (cheers!), now implement some ECDHE ciphers and make it the lead priority. Guide for sysadmins for their servers: https://weakdh.org/sysadmin.html
FascistNation
10 years ago Place Archives
2.3KViews
0likes
0Comments
Cox changes SSL iPhone 12 Users cannot send e-mail.
I have a new iPhone 12. My Tech and I have now spent almost 12 hours and 2 weeks trying to get COX home e-mail to be able to send on the phone. Still no results. COX blames the phone (Apple) Apple blames the carrier(Verizon) Verizon blames the e-mail host (COX) My IT tech and I have come to the conclusion that COX email servers are looking for a TLS encrypted tunnel before it will initiate an encrypted packet with SSL. The Apple phones will no longer let you choose to do this. Has anyone found a way to fix these issues? Just in case you think we have not done the obvious at least 30 times, plus had Apple support, COX support, Verizon Support all do the same things. The account has been removed and reset. The phone has been updated/. The phone has been reset. The Account has been tested on PC Windows Mail, Android Phone, Outlook 365, and Web-based (with three different browsers). they all work fine and set up with no problems. Password has been changed. We have tried using just the name as the user name We have tried using the full email address as the user name We have tried without SSL We have tried password Authentication and NTLM Authentication The phone receives e-mail, so we know we entered the right password. We have tried port Incoming 110,993,995, outgoing 25,465,587, and yes we realize this is a mix of POP and IMAP and SMTP, but we are and were desperate to try anything. We tried every combination of the above. We have deleted all other email accounts We set up an exchange account and it can send e-mail. We check time zones. DOES ANYBODY HAVE ANY IDEAS AT ALL? Also, did anyone find any solution to this same issue that over 16,000 people looked at, that has no solution and was closed before anyone could find one? forums.cox.com/.../cox-disables-ssl-and-now-iphone-users-cannot-use-mail-app
Ridemcowboy
4 years ago Place Internet
1.9KViews
0likes
2Comments