Skip to content
iBlockSpam
SMTP error code · Microsoft 365 / Outlook.com

550 5.0.350: generic error from the recipient's server

550 5.0.350 Permanent failure (5xx): the message bounced
By iBlockSpam Team Checked against sources 2 sources How we check our content
What it means

Exchange Online wraps a non-specific rejection from the recipient's mail system in 5.0.350. Two variants, x-dg-ref header too long and AS345, have specific fixes.

What the bounce says
Requested action not taken: policy violation detected (AS345)

One of the specific variants listed in Microsoft's article on 550 5.0.350.

What 550 5.0.350 means

Microsoft calls 5.0.350 a generic wrapper that Exchange Online uses for a wide variety of non-specific errors, typically returned by the recipient's email organization. The NDR's "Diagnostic information for administrators" section contains the original error from the remote server. That text, not the 5.0.350 code, tells you what really happened.

Two variants have their own fixes. If the NDR also says "x-dg-ref header is too long", the message was sent in Rich Text Format from Outlook, likely with an attached email message that itself has an attachment. Microsoft explains that in Rich Text messages the attachment's data becomes part of the X-MS-TNEF-Correlator header, which can grow too long for the receiving server. The fix is to send in HTML format; admins can also control TNEF settings for remote domains and mail contacts.

If the NDR says "Requested action not taken: policy violation detected (AS345)", the message has an attachment, such as a Word file, with 20 or more embedded files. Remove some embedded files and resend. For every other 5.0.350, Microsoft says there's typically nothing support can do, because the problem lies with the recipient's email system.

Likely causes

  • A rejection from the recipient's server that Exchange Online reports with this generic code.
  • x-dg-ref header too long: a Rich Text Format message with nested attached messages.
  • AS345: an attachment containing 20 or more embedded files.

How to fix it

If you sent the message

  1. Read the diagnostic section of the NDR for the remote server's original error.
  2. For x-dg-ref: switch Outlook to HTML format for the message and resend.
  3. For AS345: remove some of the embedded files from the attachment.
  4. Otherwise, forward the NDR to your admin or contact the recipient's IT team with the full error.

If you're the recipient or their admin

  1. Check your own server's logs for the original rejection reason and adjust the policy if the mail is wanted.

Frequently asked questions

What does the generic 550 5.0.350 code actually tell me?

Only that the recipient's system rejected the message for a reason Exchange Online didn't map to a specific code. Look in the NDR's diagnostic information for administrators: it contains the remote server's original error.

How do I fix 'x-dg-ref header is too long'?

Send the message in HTML format instead of Rich Text Format. Microsoft explains that Rich Text attachments are carried in a header that can grow too long for the receiving server, especially with attached messages that have their own attachments.

Sources

  1. Fix NDR error 550 5.0.350 in Exchange Online (Microsoft Learn)
  2. Email nondelivery reports (NDRs) and SMTP errors in Exchange Online (Microsoft Learn)

Provider messages are quoted as the provider publishes them. Servers can change their wording, so the bounce you received may differ slightly.