Last 3 years intermittently getting AUP#CXSNDR error on outgoing e-mails - now constant.
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.
Cox Censorship? Reopened!
Previous post, with title "Cox Censorship?" (from April 2019) was closed after a non-answer posting from a Cox rep. I have had the exact same problem today, and it is not going away by itself: (1) I try to send an extremely short email, from my MacOS Mail account, via the Cox SMTP server, with the "From" address as any of my 3 Cox email addresses, with the format XXXXXXXX@cox.net. Note that my Mail installation has been configured to send and receive email via all 3 Cox accounts/addresses since I bought the iMac in January 2020. (2) That short email contains the word "TEST", followed by whitespace, followed by a valid URL for a local business (FORMATTED AS PLAIN TEXT) which I am certain is not on ANY VALID BLACKLISTS as spammers, followed by more whitespace, and finally by another word "TEST". The subject of that email is "TEST", and the target address is XXXXXXXXXX@gmail.com. The plain-texted URL is "hascosb.com". (3) As described in the closed email, Mail thinks awhile, shows a sending progress bar, and then pops up a dialog stating that Cox rejected the message, EXACTLY THE SAME AS IN THE POSTING CLOSED AFTER COX DECLINED TO ADDRESS THE PROBLEM: "The server response was: <xxxxxxxxx@cox.net> message rejected. Refer to Error Codes section at https://www.cox.com/residential/support/email-error-codes.html for more information. AUP#CXSNDR" (Obviously, "xxxxxxxxx" replaces my actual user name, as it did in the original post.) A bunch of experimentationdemonstrates irrefutably that some service (probably malfunctioning or poorly-written security) running on Cox's SMTP server is solely responsible for this unnecessary and inane failure: (1) I can order Mail to send the exact same email without the URL from any of my Cox addresses (ie using Cox's SMTP server), and the email goes through to the target Gmail address. (2) I can order Mail to send the exact same email WITH the URL from my GMAIL address (ie using GOOGLE's SMTP server), and the email goes through to the othertargeted Gmail address. (3) I can order Mail to send the exact same email withthe URL DISGUISED("xyzhascosb.comfgh") from any of my Cox addresses (ie using Cox's SMTP server), and the email goes through to the target Gmail address. Clearly, Cox's security service(s) is(are) searching through my emails for URLs that Cox has, for some obviously invalid reason, chosen to blacklist, and then refusing to send the email. I, like most Cox customers in the Santa Barbara/Goleta area, am paying ridiculously high monthly feesto Cox for this kind of poor service. Functional email is one of the services that Cox is supposed to provide for those exorbitant monthly fees. The ignorant, irrelevant responses posted by, and premature closures imposed by, Cox reps to complaints like mine today, indicate how little Cox cares about providing adequate service to the customers of the monopolygranted to Cox by the cities of Santa Barbara and Goleta. In the anticipated absence of a cogent, productive reply from Cox's actual tech support department, it would seem that the only recourse I (and others experiencing the same persistent, uncorrected failures in Cox's email service) have is to stop using my Cox email addresses, in favor of a different provider (like Google). The downside of this approach is that we pay Google for the service by allowing them to scan our emails and sell the gathered info to advertisers. However, Google does provide relatively accurate spam filtering, so when I get spam (possibly from entities to whom Google sold my preference info), I just block it manually if Google doesn't block it automatically. Generally, Google's email service is MUCH faster (through Safari, Firefox, Mail, and Thunderbird), and has not yet refused to securely send an email containing a URL that is not on any general blacklist for any good reason. I hope that Cox proves me wrong about simply declining to address or fix the problem properly before closing or removing this post.
Cox email censorship?
I've been trying to send an email from my Cox account to another Cox account and when I do, I get: An error occurred while sending mail. The mail server responded: <xxxxxxxxx@cox.net> message rejected. Refer to Error Codes section at www.cox.com/.../email-error-codes.html for more information. AUP#CXSNDR. Please check the message and try again. The email is long and has the following link in it to a government website: https://www.azleg.gov/FormatDocument.asp?inDoc=/ars/33/01804.htm&Title=33&DocType=ARS When I remove the link, the email goes through just fine. If I send a short sentence with this link, it goes through just fine. But long text with this email and I get the error. When I call support, they tell me that I need to spend $10/ month on a support plan and they will help "fix" my Thunderbird email client. Rep says that if the problem ends up being on Cox's end that they will not give me a refund. Is this a ploy to make more money from us? I am baffled why this would be a problem on my end. Also today I tried to respond to a perfectly valid commercial email message today and same error message. I have not played around with removing content, but this is unacceptable.