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 continue to have problems sending e-mail via either Thunderbird 60.6.1 on my HP Win10 laptop or my iPhone running plain ol' mail. I can receive (POP) but cannot send (SMTP). I've had an open support ticket since Thursday April 25. I've called in multiple times and am 7 days into a promised 24-48 hour managerial callback.
Yeah, tried both ports and still nothing is received at the intended destination email address. Email shows in the sent box, but never gets off the server. Several people are experiencing this issue. As I’ve stated before, without even using the email client and only using the Cox WebMail, same issue happens. No one is receiving my Cox emails. Different day, nothing has changed.
Well I spoke to soon. I just tried to send e-mail from a location other than my home / Cox service location and all of the same old failures are back for both my Win10 laptop running the latest version of Thunderbird and for my Verizon iPhone. Cox, do you really expect to stay in business????? You're making it very hard for me to do so ....
Please review Cox support ticket CUI7952488 opened 4/25.The error message when attempting to send mail from my laptop reads "An error occurred while sending mail: The mail server sent an incorrect greeting: cxr-obgw-5004a.stratus.cloudmark.com cmsmtp 126.96.36.199 blocked. Refer to Error Codes section at www.cox.com/.../email-error-codes.html for more information. AUP#CXDNS."
I have checked multiple RBL resources and this IP address is *NOT* listed on any of them.
When sending from my iPhone the SMTP connection simply times out.
Chris,"Using our webmail would be an effective workaround"???? Thanks for a good laugh to start the day. I manage multiple e-mail accounts (7) from multiple ISPs within a single install of Thunderbird so the effective loss of all of my shared contacts and archives along with the ability to readily switch among sending accounts makes any use of your exceedingly archaic web mail a non-starter.
If this is the same Tier 2 'Chris' that I spoke with via phone back on May 13 then why did you simply tell me to change port back to the originial 465 if there was an rDNS issue? Granted that fixed the issue while I was on my home network, but it did nothing for my access from other locations. You had all of the case notes in front of you ...
As to the rDNS suggestion, there's nothing of any substance regarding reverse DNS lookups (and Cox's associated requirements) on the page that you have linked. And you fail to explain why this all changed on 4/25 with Cox's "security upgrades" and why none of my other e-mail accounts from this same IP address have no issues with my SMTP mail traffic.
A new support case was opened on 5/24 and I am still awaiting callback.