Client Portals

If you are an existing Greenwire customer, please use one of the following links to log in.
Remote Support
Client Ticketing
Client Invoicing

Additional Support

(239) 444-5522

How to Fix Godaddy: 552: Message rejected for spam or virus content

Greenwire® > IT Tech Support Articles  > How to Fix Godaddy: 552: Message rejected for spam or virus content
GoDaddy Logo Head

How to Fix Godaddy: 552: Message rejected for spam or virus content

The Short Answer

The short answer to this question is, leave Godaddy (link to official forums, over a year old). I’m not saying this out of spite or any distaste for Godaddy, but it is an ongoing issue that has only affected them. Furthermore, they are the only ones that can resolve it.

What’s the problem?

To explain what’s going on here, first we need to explain how mail providers combat spam. Typical spam filters use a point system to determine how reputable an email is. These points affect whether or not a mail is viewed as reputable enough to be delivered or not. Mail that meets this threshold for trust is typically delivered, and mail that does not is typically either marked as spam or treated with additional scrutiny.

Examples of Things that Build Trust

  • Properly configured SPF Record
  • DKIM Signed Email
  • Reputable SMTP Sender
  • Reverse DNS name matching name of sending Server

Examples of suspicious traits

  • No SPF Record, or sending from unlisted server
  • Coming from a SMTP Server with a history of bad behaviour
  • E-mail never received from recipients domain

Now, typically the goal of e-mail administrators is to build as much trust as possible in the eyes of the receiving mail server. Typically e-mail admins will go to great lengths to maintain deliverability.

The GoDaddy Problem

This all started a few years ago, when Godaddy actively decided that they could not fully control the amount of fraudulent spam e-mail coming from their servers. As a result, Godaddy was blacklisted as a mail provider on the major mail blacklists. Although they are no longer being fully blacklisted, all mail from Godaddy is immediately treated with suspicion. That means that unless your mail is otherwise perfectly trustworthy, just being from Godaddy is enough to have your mail marked as spam.

This doesn’t necessarily mean that you’re e-mail will be marked as spam every time, but it does mean that a certain number of messages will depending on how the receiving providers spam filter is configured.

What’s the Solution?

Leave Godaddy for mail. Godaddy is definitely not bad for a lot of services. We use them for SSL Certificates, Domain Registration and DNS. That said, we actively move as many clients away from Godaddy email hosting as quickly as possible. These issues can strike at any time, and can cripple a business.

My recommendation is definitely either Google Apps or Hosted Exchange. We’re a Fort Myers IT Consulting Company certified to provide both of these services if you need a consultant.

Greenwire Technology Solutions
1 Comment
  • Gerry Blevins
    Posted at 9:33 pm, April 28, 2015

    If you get this error the easiest way to fix it is thru this process. My web design client had the same issue and this is the fix all for this situation.

    Likely when this situation has arisen with your site’s domain name it means that your site is either sending viruses or spam. If you legitimately have no clue what’s going on, your not sending spam / newsletters from your domain and your not infected with any virus then probably your using WordPress or a PHP / Database driven site and it has became compromised. Go to this website first.


    Check your site to see if it’s infected with any malware. Godaddy isn’t as helpful in this situation but they did tell me who does all the blocking for them so once you get a clean bill of health and your ready to start sending email again you’ll go to this URL to unblock your website.


    Fill out all you information. In the IP spot your going to want to input the IP number to GoDaddy’s email server. This IP is listed in the refusal email that was sent to you with the 552 error.

    In the space where you put in the 552 error string, you need to copy it EXACTLY how it is in the email. There are identifying parts to this string which their form knows if it’s from their servers so you’ll need to paste ALL of that string. If the form accepts your submission then you filled out all the information correctly.

    When I did this for a client it resolved all her problems and Cloudmark handled the problem in less than an hour.

Post a Comment