middlejim
New Contributor II
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: Cannot sent emails to any cox.net email address using third party clients
Thanks for the prompt reply, Allan. Note I am also Middlejimbo...had to create a new name to re-join Forum for some reason. I am not using a VPN. I get why you are suggesting a router bypass, and I will perform that experiment this evening, but a router filter doesn't explain why cox-to-cox mail are showing up in my Cox WebMail "Sent items" folder if they were not making it past my home network? You are free to dig around in my WebMail to analyze those sent-but-never-received items. UPDATE: In an attempt to avoid sending cox-to-cox for a mass email (~100 addresses, which includes multiple cox.net recipients), I originated the email from my outlook.com address. I received an Undeliverable notice listing all of the cox.net addresses indicating timeout due to "450 4.4.318 Connection was closed abruptly (SuspiciousRemoteServerError)". When I sent the exact same email to a single cox.net addressee from my outlook.com address, and it went through without error.28Views0likes1CommentRe: Can't send email to other Cox accounts
KevinM2, I'm sharing this info and question for the common good of the Forum public. UPDATE: My issue was inability to send from one cox.net address to another within my household (or even self test) on three device types: iPhone SE with default Mail app (IMAP); Android 7.0 phone with BlueMail (IMAP); and two PCs running Outlook 2013 mail client (POP3). Self-test mail sent from these apps would appear in the Sent folder of the apps. For the BlueMail app they would also appear in the Sent folder of the associated WebMail account. In no case would the self test mails make it back to the Inbox destination. Mail to and from external non-cox domains was fine. After following all of the suggestions, I replaced the mail apps on the iPhone and Android with Outlook mobile and set them up using the automatic IMAP / SMTP Cox settings. ALL GOOD. Thinking I was on a roll, I updated one of my PCs (Windows 10) to Office 365 which includes Outlook for Office 365 (16.0.11601.20130) 64 bit. I used the automatic POP3/SMTP configuration for Cox: Incoming port 995 SSL/TLS encryption, outgoing port 465 SSL/TLS. ISSUE PERSISTS. Self test mails appear in the Sent folder of the Outlook app, but not in the Sent folder in the Webmail app. Issue appears to be outbound from app to cox. I have never had an issue with mails appearing in the Webmail Inbox missing from any of my app Inboxes at any point in this effort. QUESTION: If I subscribe to Cox Complete Care, will I get a support rep with sufficient expertise in 3rd party mail clients to work this issue?0Views0likes1CommentRe: Can't send email to other Cox accounts
Just updated password for one of my mail accounts. Issue persists. I am able to send and receive mails via the myemail.cox.net web app, but I would prefer to use my Outlook app on my PC! It used to work!! I am having the same issue now with my Android phone BlueMail app and my wife's iPhone mail app.0Views0likes3CommentsRe: Can't send email to other Cox accounts
Thanks JonathanJ. I did ensure settings per Cox directive: inbound POP3 port 995, SSL checked, outbound SMTP port 587 with TLS encryption. I do not know the version of TLS used by the Outlook 2013 app. No change. Still passes the Outlook app self test, but as with the other SMTP settings (with SSL selected), I do not get the Microsoft Test Message in my Inbox as I did before, and I am unable to send mail between cox.net accounts if I originate from the Outlook app (even cox.net addresses outside the three associated with my account).0Views0likes5CommentsRe: Can't send email to other Cox accounts
I am experiencing the same issue, which started some time earlier in the month of April 2019: I am unable to send email from one Cox account to another Cox account when the mail originates from the Outlook app (or any of the accounts to themselves). If I originate the mails from Cox Webmail, I can send mail to my other accounts (and to themselves), and I will see the incoming email in the Outlook app Inbox for the respective account. Thinking this is some kind of breakdown between the Outlook app and Cox mail, I tried setting up an IMAP account in the Outlook app, but same issue -- cannot self test or send mail to other Cox accounts if I originate in Outlook. Changing to IMAP changes the incoming server, and the issue appears to be in the outbound (SMTP) path between the Outlook app and Cox. All other email traffic to and from any address that is not cox.net seems to work. I have three cox.net mail accounts associated with my cable account. All PCs are Microsoft running Outlook 2013, using POP3 accounts set up per latest Cox directive. I just set up an IMAP duplicate for one of these in my Outlook app to see if the issue was POP3 related, but as I said, no improvement. Not a critical issue, but is an enormous pain when I want to forward stuff to my wife, etc. Is this some kind of change in Cox security protocol?? Ideas please!!30Views1like10Comments