- Hello, I cannot send emails from my MacAir, despite manually checking settings and re-entering my password. I am getting message that my iCloud(XX@icloud.com) sender was rejected. The error code provided was AUP#CXSNDR, which apparently means 'Your email failed authentication checks against your sending domain's SPF, DomainKeys, or DKIM policy." How do I fix this?? I saw a great post from early this year with directions that I followed today without success: "There is a bug in the macmail software. you have to change the outgoing mail server settings to manual, and the make the settings to 465, outgoing server requires authentication. and password. Make sure you erase the dots currently in the password field and then re-enter the password. I used to beta test for Apple, and I know that bug well. I actually reported it when they went from 10.4 to 10.5, a decade ago, and they STILL haven't fixed it. Also, ensure, prior to doing all this, delete everything sitting in the outbox." Thanks!!
- I cannot send emails through the Outlook app on my Macbook and I can't send emails on my iPhone through the mail app while I am on the internet. I can send emails when my phone is using its 5G or when my computer is using my phone as a hotspot, but if I am connected to wifi I can't send anything. This is the message I would get when the emails wouldn't send. cxr-obgw-6002a.stratus.cloudmark.com cmsmtp 18.104.22.168 blocked. Refer to Error Codes section at www.cox.com/.../email-error-codes.html for more information. AUP#CXDNS Error Code: -17099 Then I was doing some digging and I was able to send a few test emails when I turned off my SSL connection on my computer but it stopped working after a while. And this is the message I would get. Connection to the server failed or was dropped. Error Code: -3253 I get all my emails sent to me but I cannot send them when connected to my wifi. I currently am not using Cox internet because I moved to an state that does not provide Cox as an option and my parents are my account holders, they made me an email account under theirs. I am currently using Xfinity internet but I cannot send emails on my phone on my work wifi either. Something is wrong with the SMTP and SSL connection and needs to be fixed on 3rd party email platforms because I am not logging into my webmail every time I need to send an email.
- I highlighted a few emails, one from homedepot.com and click SPAM instead of delete. After clicking "Not spam" on them. I no longer receive verification emails from Homedepot.com. I checked all the setting i can to make sure that domain is not blocked but i still can't receive verification code emails from homedepot.
- Occasionally I would get this error, but it would pretty much only pop up when trying to save a copy of the e-mail in the Sent folder. At first I figured it was just a weird permissions issue, or maybe even possibly when sending to specific servers and there was some weird glitches going on between the different servers, but now it's a constant thing. I'm even getting this when trying to send e-mails to my father and grandfather, who are both on the cox.net domain - personal accounts that were given out when Cox didn't determine that having to give e-mail addresses to their customers was too "burdensome" or "costly". In looking at the codes on your page with them https://www.cox.com/residential/support/email-error-codes.html I don't see one that has both AUP & #CXSNDR, but from my powers of reading and deduction it seems it's a mishmash of: AUP - which is Email sending blocked due to suspicious account activity on primary Cox account. To secure your account, please reset all Cox account passwords at cox.com/password. Contact Cox at cox.com/chat to remove block and reference error code AUP#CXMJ. The fix: Reset your password at www.cox.com/password or visit www.cox.com to sign in to your primary Cox account and go to the My Profile page. Then, contact Cox at www.cox.com/chat to remove the block referenced by error code AUP#CXMJ. CXSNDR - There was a problem with the sender's domain. The fix: Your email failed authentication checks against your sending domain's SPF, DomainKeys, or DKIM policy. So I'm not sure what to do here. When this initial problem came up about 3 years ago, I e-mailed Cox tech support, had a little back & forth with them (they seemed utterly confused), then I quit getting responses from them regarding this, even when I initiate a new support e-mail. I'm guessing that along with free e-mail addresses to your customers, you've determined that trained tech support is too "costly" and "burdensome" as well. Or who the hell knows, maybe just having tech support at all is too "costly" and "burdensome". Who the hell do I talk to to get this fixed? Since I'm forced to be reduced to guessing what's going on here since it would appear that Cox's "key" for the different codes is obviously woefully incomplete, I'm guessing that my account has been flagged for "sending spam" (AUP), which then causes the secondary error (CXSNDR); which is simply baffling as the only things I really send out from this e-mail address are historical e-mails to my father, grandfather and a few others as well as sending links about news or other things of that nature. The only other stuff I get is the few newsletters I subscribe to and then of course the "confirmation" e-mails when I need to start a new account somewhere. Can someone (presumably in tech support - preferably even someone that's trained/knowledgeable) help me figure out what the hell is going on here and help me rectify it? I realize that since Cox has determined that customers having Cox.net e-mail addresses is too burdensome and costly, it's "better" for the company to drive off everyone still using those e-mail addresses so they can save money (while driving the price for services up - naturally), but I'm not about to change an e-mail address I've had for two and a half decades. Or is competent tech support something you have to pay extra for these days with your "Complete Care" package? You've already made it elusive as hell to find an e-mail address to open up a new dialog with tech support, so it honestly wouldn't surprise me. This happens with Apple Mail (iOS & MacOS), Thunderbird (on both Linux & MacOS), Cox's webmail in an Internet browser (tried on 4 different browsers in various states of configuration), This needs to be fixed, balls in your court Cox. Also since I'm dropping valid complaints about the erosion of service and support from Cox, there's also the giant problem with my inability to send an e-mail when connected to my VPN. The last administrations acts against Net Neutrality should have sufficiently scared the *** out of anyone who valued their privacy (hence the drastic uptick of VPN providers in the last 5 years), but it would appear that Cox is always one step ahead when it comes to ruining any semblance of privacy one might have enjoyed with them blocking connections to VPN providers should one need to send an e-mail. Again - this is something I've brought to the attention of tech supportmultiple times and they've simply sat there in silence with a presumably quizzical look on their face. They had no god damned idea what a VPN was. Whether that's due to insufficient training on Cox's end or simply a "business tactic" to get people to pony up EXTRA for basic tech support I'm not sure; I wouldn't be surprised by either frankly, but I'd put my money on the latter. These aren't unreasonable requests. Just so we're clear, I need to: Be able to send email Be able to send email when connected to my VPN. That simple guys. It's really that simple.
My outgoing mail not sent. System administrator gives error message of CXSNDR There was a problem with the sender's domain. Your email failed authentication checks against your sending domain's SPF, DomainKeys, or DKIM policy..CXSNDR There was a problem with the sender's domain. CXSNDR There was a problem with the sender's domain. Your email failed authentication checks against your sending domain's SPF, DomainKeys, or DKIM policy. Your email failed authentication checks against your sending domain's SPF, DomainKeys, or DKIM policy.
- Can’t Access E-Mail using Outlook or Mac Mail (Error Code 3170) Starting on 10/2/19, I’ve started getting the following error message: “Outlook cannot find the server. Verify the server information is entered correctly in the Account Settings, and that your DNS settings in the Network pane of System Preferences are correct.” I made no changes to my Outlook e-mail client; this just started happening out of the blue. Then as a test, I attempted to download my e-mail via Mac Mail. This also failed to connect, just got a spinning wheel that forced me to use a “force-quit” to get out of the Mail app. I updated my Cox password and also tried resetting the modem. It should be noted that I’m able to access my Web Mail via Cox’s main website; no problems there. Because I cannot access my e-mail using two separate e-mail clients, I strongly believe that the problem is with Cox. My system details: Outlook for Mac 2011 (14.7.2) Mac Mini running Sierra 10.12.6 Although I’d made no changes to either e-mail client, I reviewed the Port settings for both servers (993 and 465) to make sure they were correct. The “Use SSL to connect (recommended)” check boxes are checked for both Incoming and Outgoing. For Authentication I have “Use Incoming Server Info” applied (I also tried “User Name and Password” to no effect). I’ve had issues with my Cox e-mail several times in the past, so I’m quite familiar with how to set up my e-mail clients with the correct information. I would greatly appreciate any and all assistance, advice, help! Thanking in advance...Solved
- The link first takes you tohttps://myemail.cox.net/appsuite/,then it loops to this link:https://idm.east.cox.net/affwebservices/public/saml2sso?SAMLRequest=,then it loops back to the first link. It repeats this cycle over & over. Tried this in Chrome and FIrefox web browsers, no ad blocker running or popup being blocked. Tried on multiple days. Tried on two different Windows 10 computers. Don't think the issue is me. Does these links no longer work or is the webmail access down?
- I have this issue where I'm not receiving emails when I'm supposed to, and I'm worried that I can't send any either since when I try to send myself an email, it doesn't show up. I noticed this issue about a week ago now. Does anybody know what might be causing this?