Read the forum guidelines
Since the 4/24/19 email security rollout, users have been experiencing various kinds of email issues. This is now day 13. I can receive email, but when I send email, it shows in my sent box, but is not received by the intended recipient. It is stuck on the Cox email server. My IP address is not blocked, I verified that. This is happening on my new iPad iOS 12.2 and on Cox’s WebMail page, no matter what browser I try. To date: nothing has been resolved. Every fix, workaround, password change, delete and re-entering email address, blah-blah-blah, etc. has failed. Been working on this for 12 days straight.
Please, I would like to hear from all of you what your current status is concerning your email and, if any, what fixes have worked for you.
Please keep the responses coming, we’re really starting to get some strong answers to the email issues supplied by us, not Cox. Awesome!!!
Link to my original post:
Contributed by WiderMouthOpen:
You can also see it in a tracert. Notice at hop 6 it leaves Cox and is on a provider called RackSpace. Don't know if they are the email provider or network provider for the email provider, but the thread you quoted shows it's now a partnership.
Tracing route to imap.east.rs.oxcs.net [18.104.22.168]over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]2 6 ms 6 ms 8 ms 10.1.128.13 8 ms 7 ms 9 ms 100.120.244.804 8 ms 9 ms 9 ms 100.120.244.1925 18 ms 17 ms 18 ms ashbbprj02-ae1.0.rd.as.cox.net [22.214.171.124]6 18 ms 18 ms 19 ms aggr501a-94-core9.iad3.rackspace.net [126.96.36.199]7 * * * Request timed out.8 19 ms 35 ms 17 ms coreb-dcpe2.iad3.rackspace.net [188.8.131.52]9 19 ms 17 ms 20 ms core9-coreb.iad3.rackspace.net [184.108.40.206]10 18 ms 18 ms 18 ms aggr501a-65-core9.iad3.rackspace.net [220.127.116.11]11 19 ms 18 ms 17 ms 18.104.22.168
FYI that was a tracert from my computer to imap.cox.net. The confusing part is because of the "partnership" they made changes in DNS too.
C:\Users\>nslookup imap.cox.netServer: router.asus.comAddress: 192.168.1.1
Non-authoritative answer:Name: imap.east.rs.oxcs.net <==Address: 22.214.171.124Aliases: imap.cox.net
Notice how imap.cox.net automatically redirects to the new domains on oxcs.net, which is not a Cox server.
Thank you all in advance.
I've been searching for solution as many of you but apparently there is no solution. COX support was useless.
I can receive my emails through my iPhone X and no issues with incoming or outgoing emails with my imac/macbooks at home or via webmail.
I just can't send emails through my iPhone,even after verifying the settings, deleting and re-adding the email accounts, or changing the passwords.
I also have no problem receiving and sending emails for my work emails on my iPhone so it's definitely something to do with the Cox email server.
I hope there will be resolution soon.
After I posted the above, I reread some of your posts and I just concluded I have the same issue with Steve A. I can send emails through my iPhone once I disconnect from my work WiFi. Not sure why this is the case now since I also didn't have any issues prior to April 2019.
I'm not 100% certain but I think my issue when I'm at work on wifi is that my company doesn't provide a Reverse DNS lookup for when the Cox SMTP servers are trying to accept my SMTP connection and authenticate who I am. Just like you.... when I'm at home on WIFI or just on AT&T cell service everything works OK. I've already asked our firewall people here at work to see if packets are flowing from our network out and back to/from SMTP.COX.NET port 465 and the packets are going back and forth and not being blocked. BUT....apparently if Cox can't get a good result from the reverse dns lookup then they reject your connection. If you look in other threads you'll see this mentioned by Cox support. Look in this discussion:
I've asked my company if they can allow the reserve dns lookup and I was told No that because of security reasons they won't. So....if I need to send an email from my iPhone when I'm at work I then have to turn off WIFI to go back to AT&T wireless and then send the email.