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-app1.9KViews0likes2CommentsError when accessing web page Error code: SSL_ERROR_RX_RECORD_TOO_LONG
I am unable to access my work website (https:akcost.com). I was able to but now it has stopped. I am able to access it using the IP Address (24.237.182.162) but not the name. Does not matter if I use Mozilla or Internet. C:\>ping 24.237.182.162 Pinging 24.237.182.162 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 24.237.182.162: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss) C:\Users\Ginny Wright>cd.. C:\Users>cd.. C:\>24.237.182.162 '24.237.182.162' is not recognized as an internal or external command, operable program or batch file. C:\>ping 24.237.182.162 Pinging 24.237.182.162 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 24.237.182.162: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\>ping akcost.com Pinging akcost.com [2001:470:0:11c::403e:ac25] with 32 bytes of data: Reply from 2001:470:0:11c::403e:ac25: time=37ms Reply from 2001:470:0:11c::403e:ac25: time=36ms Reply from 2001:470:0:11c::403e:ac25: time=37ms Reply from 2001:470:0:11c::403e:ac25: time=37ms Ping statistics for 2001:470:0:11c::403e:ac25: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 36ms, Maximum = 37ms, Average = 36ms3.9KViews0likes6CommentsWhen 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.html2.3KViews0likes0CommentsCannot log into Secure Sites
Don't know what happened, but we have lost all SSL sockets across our whole network. Cannot even log in to yahoo fantasy or ebay! We have 3 computers with XP, Vista and 7 and NONE of them can log into anything! I tried reseting the modem and the router. Still nothing different. I checked all settingsfor SSL in all 3 computers. Nothing different.I even went as far as doing system restores to the computers, still nothing. I am really thinking this is not my computers and something has happened between my network and cox....why would all 3 different operating systems just stop working? It's just not logical. Is it possible something in thecox signal is messed up and my path is notsecure? I have not done anything with the "New 1GB" Service, updates, or new modem.Still using my Motorola...connection is fine, speed is fine, can internet anywhere, just cannot LOG IN anywhere, cannot BUY anything... When I click log in or checkout, the next page just says The page cannot be displayed check your internet connection, but the site's are not able to switch to HTTPS...anything httpworksfine... Has anyone had this problem? Any thoughts of a fix?2.9KViews0likes5Comments