Fix email delivery issues for error code 451 4.7.500-699 (ASxxx) in Office 365

Getting an error when you send an email can be frustrating. If you get a "bounce" message, also called a non-delivery report (NDR), for error code 451 4.7.500-699 (ASxxx), this topic can help you fix the problem and get your message sent.

email user symbol

I got this bounce message. Help me fix it.

Administrator symbol

I'm an Admin. How can I fix this?

Why did I get this bounce message?

You received this bounce message with error code 451 4.7.500-699 (ASxxx) because the connecting IP address changed its previous sending patterns, and started sending much more traffic than it had before.

This error code is part of anti-spam filtering in Office 365. You get this error when the IP address that is sending you email changes significantly from its previously-established sending patterns. It is part of a filtering technique known as graylisting. When new senders appear, they are treated more suspiciously than senders with previously-established history.

This error response is called IP throttling, and it can help prevent you from getting more spam email.

I got this bounce message. Help me fix it.

If you sent an email and got this bounce message in response, try doing the following:

  1. If your organization uses Exchange Online Protection (EOP), an admin can take steps to help prevent the problem (see the next section).

  2. If your organization does not use EOP, for example, if you provide a third-party service, the error will resolve itself as you slowly ramp up your email traffic over a period of a few days and you establish a sending history with Office 365.

If the problem continues, send the bounce message to your email Admin for assistance and refer them to the I'm an Admin. How can I fix this? section below.

I'm an Admin. How can I fix this?

There are a few ways to fix this problem if you're an Exchange Online Protection (EOP) customer:

  1. If you're trying to relay email from your on-premises email server through Office 365 to either another receiver (hosted by Office 365 or a third-party service), or to another user within your own organization, then to remove throttling from this scenario you should set up a connector to configure email flow from your email server to Office 365.

  2. If you're receiving inbound email but you have another third-party service or on-premises appliance in front of Office 365, then to remove throttling, you should set up a connector to apply security restrictions to mail sent from your partner organization (or on-premises device) to Office 365.

After you set up a connector, you can validate your connectors in Office 365.

Although you can send mail from your domain, we don't recommend using the domain in production environments due to problems with filters and other limits imposed on the domain. For standard environments, customers should add a custom domain. For more information on domains, check out this Domains FAQ.

Expand your Office skills
Explore training
Get new features first
Join Office Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.