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 [184.108.40.206]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 [220.127.116.11]6 18 ms 18 ms 19 ms aggr501a-94-core9.iad3.rackspace.net [18.104.22.168]7 * * * Request timed out.8 19 ms 35 ms 17 ms coreb-dcpe2.iad3.rackspace.net [22.214.171.124]9 19 ms 17 ms 20 ms core9-coreb.iad3.rackspace.net [126.96.36.199]10 18 ms 18 ms 18 ms aggr501a-65-core9.iad3.rackspace.net [188.8.131.52]11 19 ms 18 ms 17 ms 184.108.40.206
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: 220.127.116.11Aliases: 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.
COX SMTP servers now longer works for some internet connections. It is throwing a CXDNS which means that it is blocking all addresses that cannot be reverse DNS lookup-ed, but some addresses cannot be DNS lookup-ed. We have Frontier internet and address they give us does not have a DNS entry. If I switch my Google Fi Android phone to the cellular network, the SMTP works (because the name is DNS resolveable).
I have not been able to send emails from my iPhone using the Mail client in the phone ever since 4/24 but only WHILE I'm at WORK on WIFI. I can't even reply to one of my own emails and can't send a Reply to myself. BUT....once I turn off WIFI and go back to AT&T or go home and use my home WIFI it works Ok. Yes....I have performed all of the recommended port and security settings. Yes....I can send email to myself and Reply to that same email if I'm using your webmail in a browser. Yes....I've done as Cox recommended and I got the IP address from when I'm attached to work WIFI and then checked the ip address to see if it's blocked using the Cox web site that you had previously recommended and the IP address from work is not blocked.
BTW....I was never informed of any of these Cox email security changes. I never received a flyer in my monthly bill and I never received an email from Cox to my primary email account warning me of these impending changes. The only way I found out about these changes was from reading these Community postings. You must have a huge number of Cox customers that are having issues and don't even realize that these Community forums even exist.
SO....bottom line is that I can not send any emails to anyone (including a reply to myself) while I'm attached to my work WIFI. This was all working before 4/24.
Here’s what I sent to Cox.email@example.com, I truly hope they receive it.
The administrator, KevinM2, on the Cox Community Forum wanted me to forward the links on that forum so you can see the major issues I’ve been having with my email since the 4/24/19 Email Security Rollout.
My hope is that, if you do indeed receive this email, that you will read every bit of info contained in these threads and forward this info to the IT Divisions Department Administrator. For the last 12 days, I have been with Cox chat rooms for customer support and on the Cox forum doing everything that has been asked of me with no success, over and over again. I can’t tell you how many times I have deleted and created new passwords, deleted and re-added email addresses, reviewed my profile for any changes, which there were none. I don’t even use the email client on my new iPad with iOS 12.2 with TLS 1.3 which is totally ridiculous. I am reduced to only using Cox WebMail using Safari. I can receive out side email with no problem, something that Cox fixed because at one time I could not. The major issue is simply this: using a Safari (I have tried several other browsers with the same results) I login to the Cox WebMail page and create an email and send it. I supposedly sends the email and the sent email box has the email in it, not the outbox since the email was supposedly sent. The problem is the the recipient of that email never receives the email I just sent. I have been testing this for the last 10 day with my Son and he has yet to receive any of my test emails at his ATT.net and Gmail.com email accounts. He can sent me email from those same email account and I receive them just fine. Outside of Cox, no one is receiving my emails. The Cox WebMail shows the email as sent, but the actual emails are queued somewhere on the Cox servers. I never get a bounce back that the email was blocked or non Cox email server is not available. Just nothing.
I hope you receive this email and you can help in some way.
Thank you for your time and help.
Thanks for the tip, SpongeBob128, really appreciate it. From what you just told me this is totally and absolutely on Cox. We as users have absolutely no control over whether a DNS server has reverse lookup or not. For crying out loud, we’re the customers, not the friggen IT Tech department. I hope KevinM2 reads your reply and can look into what you described. That’s the best and most logical thing I’ve read concerning Cox’s email issues yet.
Thank you so much for your reply.
Definitely a Cox problem. When you addressed email to ATT and Google, you did not get rejects. The email has yet to deliver, but you didn't get rejects.
When you addressed to a valid address on the Cox domain, you did get rejects.
These processes involve different server agents so you're getting differing results. The problem is on the server...not with your settings.