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 [220.127.116.11]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 [18.104.22.168]6 18 ms 18 ms 19 ms aggr501a-94-core9.iad3.rackspace.net [22.214.171.124]7 * * * Request timed out.8 19 ms 35 ms 17 ms coreb-dcpe2.iad3.rackspace.net [126.96.36.199]9 19 ms 17 ms 20 ms core9-coreb.iad3.rackspace.net [188.8.131.52]10 18 ms 18 ms 18 ms aggr501a-65-core9.iad3.rackspace.net [184.108.40.206]11 19 ms 18 ms 17 ms 220.127.116.11
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: 18.104.22.168Aliases: 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.
If you're sending and receiving email, your "security" issue is resolved. You now have a new problem. Either the Cox servers are not sending email or the recipient's servers are not accepting email. If you're not receiving non-delivery notices, your email is being queued somewhere.
I suspect Cox only because they've been recently tinkering with their email systems...or whoever administers it.
Exactly, my son has not received all the test email to his att.net and gmail.com email accounts. He was prior to 4/24/17. They’re being queued on the Cox outgoing SMTP servers. All the sent emails are in the sent box on Cox’s WebMail, but seem to be queued on the Cox server.
Thank you so much for your reply.