Forum Discussion

Dan_H_'s avatar
Dan_H_
New Contributor

I can't send any emails out.

So I have been experiencing similar issues that others have been stating regarding the cox servers blocking my outgoing messages.  I have tried multiple Email Clients and receive the same error.

Interestingly enough I was even receiving the error when sending out email messages from Cox Webmail.  

So I chatted with 2 different Cox chat individuals online today and neither was helpful at all.  They both wanted to get right to the survey at the end to describe how they did (which was a big mistake by the way for them).  The second person asked me to try on Cox Webmail and now it is not giving me the error messages anymore.  So it was easy for her to say - it's your email client's issue.  Which is not the case when every single email client is experiencing the same issue that Cox Webmail was experiencing until today.  

So my issue is that none of my email clients can send out emails.  Thunderbird gives the error below and does not send it out.  Windows Live Mail will store it in my Outbox for a couple of hours and will eventually send it out.  I tried EM Client and that was experiencing the same issue (but I have since deleted that software).

This forum suggests that Cox believes I am spamming (hence the not sending or in the Windows Live Mail case holding onto it for 3 hours before sending).  I believe I have my server settings correct and am still experiencing the issue.  The good news is that my Gmail account is working great.  Maybe that is what Cox wants is to me to move away from them and free up that bandwidth.  I am NOT a heavy email user (just your average Joe).  I don't have a business that sends out a ton of emails just 1 or 2 a night to a couple people.

I have not changed my password during this time.  I have had the same password during this issue.

VERY FRUSTRATING the lack of accountability.  I see the Forum leaders are responsive here and hope them or one of you can help me.  

Below are my errors messages.  

Any help is appreciated!  Thank you so much!  Sorry for the rant!


Thunderbird 45.8.0 -

An error occurred while sending mail: The mail server sent an incorrect greeting:  eastrmimpo306.cox.net cox too many bad commands from (IP ADDRESS here changed)

Windows Live Mail 2012 - 

An unknown error has occurred.

Subject 'Re: Code and Travel'
Server Error: 554
Server Response: 554 eastrmimpo210.cox.net cox too many bad commands from (IP ADDRESS here changed)
Server: 'smtp.cox.net'
Windows Live Mail Error ID: 0x800CCC6F
Protocol: SMTP
Port: 465
Secure(SSL): Yes

8 Replies

Replies have been turned off for this discussion
  • JonathanJ's avatar
    JonathanJ
    Former Moderator
    @ Dan

    Are you having the same issue on cox webmail? If not please follow the link and check setting on windows live http://bit.ly/1LvB3I2.



  • Dan_H_'s avatar
    Dan_H_
    New Contributor

    Jonathan 

    Thanks for the note.  I was having the issue with cox webmail for roughly 3 weeks and then it worked yesterday.  Today it is not working again.  The message I am receiving again is:

      The message was not sent to dqh@cox.net. There are several reasons why this may have occurred: 1) You may have exceeded the allowable sending limit via WebMail. If you have knowingly been sending numerous messages within a short time period, you may be blocked from sending additional messages for a period of three hours, at which time the block will be automatically lifted. 2) The content of your message may be considered spam by our anti-spam systems, and has therefore been blocked. Try sending an empty test message to yourself to see if you can receive it. If you receive it, this would indicate that the blocked message is considered spam. Please visit http://coxagainstspam.cox.net for more information. 3) There may be a temporary system problem or maintenance which is causing the failure. In this case, the service will be restored as soon as possible.

    I reviewed my Live Mail settings at they are set to:

    Outgoing Port 465 SSL checked Server = smtp.cox.net

    Incoming Port 993 SSL checked Server = imap.cox.net

    The funny part about Live Mail is that it will sit in my Outbox for a couple of hours and then overnight it sends it out.  (I do nothing in between that time).  So it is holding onto it and then eventually sends it out.

    Thanks again for your help!

    Dan

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @Dan H.

    These appears to all be security messages suggesting there is a problem with your account. The too many bad commands error in your initial post suggests either a malfunctioning email client or perhaps malware on one or more of your systems that is trying to compromise your account.

  • Dan_H_'s avatar
    Dan_H_
    New Contributor

    Chris

    Thanks for the reply.  If it was a malfunctioning email client would I have it happening on all of my email clients?  Also how can I tell or resolve those systems?  I have Trend Micro that is running on my machine that is pretty good at picking up those issues.  What do I try next?  Can you tell if it appears to Cox that this account is compromised?

    Thanks!

    Dan

  • Dan_H_'s avatar
    Dan_H_
    New Contributor

    Chris

    Can you tell if my account looks like it is compromised on the Cox side? 

    Thanks again for your help!

    Dan

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @Dan H.

    I'm not seeing any obvious indications of a compromise. If for example you have one mail client sending too many bad commands the server will implement a cool down period on the account which would affect all of your mail clients.

  • Dan_H_'s avatar
    Dan_H_
    New Contributor

    Chris

    Thanks for the reply.  What are my options?  I can't send anything in Cox Webmail or any of my email clients.  Do I need to open up another ticket?

    Dan

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @Dan H.

    It might be helpful to try disabling all of your email clients then adding devices back one by one and waiting to see when the problem starts again.