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 [22.214.171.124]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 [126.96.36.199]6 18 ms 18 ms 19 ms aggr501a-94-core9.iad3.rackspace.net [188.8.131.52]7 * * * Request timed out.8 19 ms 35 ms 17 ms coreb-dcpe2.iad3.rackspace.net [184.108.40.206]9 19 ms 17 ms 20 ms core9-coreb.iad3.rackspace.net [220.127.116.11]10 18 ms 18 ms 18 ms aggr501a-65-core9.iad3.rackspace.net [18.104.22.168]11 19 ms 18 ms 17 ms 22.214.171.124
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: 126.96.36.199Aliases: 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.
I know you’re busier that a one legged man in a kicking contest. I can tell because you are not completely reading my posts that describe in great detail my experiences with Cox Webemail over the past 13 days. What is the point of sending a link to all my threads to firstname.lastname@example.org? No one there will receive it. It will end up in the sent box, but you won’t receive it. All my sent emails are queued somewhere within the Cox email network. With all do respect, I’m getting frustrated doing all the leg work for the Cox IT Division. I will attempt what you as just to make you happy, but I am confident the email will not be received at Cox.email@example.com.
Thanks for stopping by.
Cox would receive it because it's a different network connection. When you send an email to another domain (ATT or Google), Cox will forward it (supposedly) on an Internet connection because it's outside the Cox domain.
If you address an email within the Cox domain, it's just a server-to-server connection. The server agent will route the email to the correct server according to the user account (for example, Cards47) as opposed to mail-server listings on the Internet. I forget the technical name of "mail-server listings" so I just made that term up.
***EDIT: (30 minutes later) Internet mail servers use Pointer Records (PTR).
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.
I just send you an email (using my work email address) of the information from my iPhone as I was trying to send emails while on the company WIFI. It contains the work ip address while on wifi and also the results of the blocklist as displayed when using the links that were previously suggested by Cox in these forums.
Please reply and let me know that you actually received this email with the information you requested.