This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Delivery Failure code 535 - authentication reject using gmail to import from cox

Have been getting this occasionally the past week or so.  If I wait a few minutes and send the same thing it will usually go through.

All settings for Cox servers including password seem to be correct.  All gmail settings appear to be correct and everything works MOST of the time.  Any ideas? 

  • Ozarkike,

    Managing your Cox email through a third party email provider is a bit beyond our scope of support, so I am hoping another forums user with experience will chime in.

    What server settings have you entered for sending?

    The Cox email server settings can be found at the following link.
    https://www.cox.com/residential/support/pop-or-pop3-server-settings.html
  • Similar issues for family members using Windows 10 and XP. One person using XP and Outlook 2003 keeps getting prompted to enter their Cox mail password to receive/send or they get an Internet Security windows about Cox trusted servers. Clicking YES removes this until the next time which is intermittent.

    Another person using Windows 10 and its Mail client has issues sending email. Sometimes it works - sometimes the mail sits in the Outgoing box. Cox points the finger at Microsoft and I'm sure Microsoft will point the finger at Cox.

    Server settings for the XP person are:

    pop.cox.net - port 995, smtp.cox.net - port 465 (with SSL set on for both)

    Server settings for the Windows 10 person are:

    imap.cox.net:993:1 (port and SSL on), smtp.cox.net:465:1 (port and SSL on)

  • ColleemD,

    Outgoing Port 465 with SSL enabled.  The authenication failure seems to

    be coming from Cox

  • UPDATE: Changed the smtp.cox.net port to 587 SSL enabled on both family member's email clients. Will try out and see what happens. Tests for outgoing/incoming from non-Cox email addresses were successful, but I'm not convinced this is a permanent fix.

  • Hi, please visit this link to see if the information helps:  www.cox.com/secureemail.  Let us know.  Thanks,