Outlook office 2003 báo lỗi remote ttem header năm 2024

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Fix NDR error "550 5.0.350" in Exchange Online

• Article
• 01/24/2024

In this article

It's frustrating when you get an error after sending an email message. This topic describes what you can do if you see error code 550 5.0.350 in a non-delivery report (also known as an NDR, bounce message, delivery status notification, or DSN).

Use the information in the NDR to help you decide how to fix the problem.

Why did I get this bounce message?

5.0.350 is a generic wrapper that's used by Exchange Online for a wide variety of non-specific errors that are typically returned by the recipient's email organization.

But, if the NDR also contains x-dg-ref header is too long, that's a specific problem with a specific solution. This issue occurs if you use Rich Text formatting in Outlook messages. The message likely contains at least one attachment, and one of the attachments is likely an email message that also contains at least one attached email message.

Or, if the NDR also contains Requested action not taken: policy violation detected (AS345), that's another specific problem with a specific solution. This issue occurs if the message contains an attachment (for example, a Word file) with 20 or more embedded files (for example, Excel or Word files).

I got this bounce message. How do I fix it?

If the NDR contains x-dg-ref header is too long, use HTML formatting for messages in Outlook instead of Rich Text Format. For more information, see Change the message format to HTML, Rich Text Format, or plain text.

If the NDR contains Requested action not taken: policy violation detected (AS345), remove some embedded files from the attachment.

Otherwise, forward the NDR to your admin for help.

I'm an email admin. How do I fix this?

x-dg-ref header is too long

In Rich Text formatted messages, the attachment's binary large object (BLOB) becomes part of the header stream in the X-MS-TNEF-Correlator header field. If the attachment is too big, the line length of the header field is too long, so the receiving email server will reject the message.

In Exchange Online, you can control TNEF (also known as the Transport Neutral Encapsulation Format, Outlook Rich Text Format, or Exchange Rich Text Format) settings in remote domains, and in the properties of mail contacts or mail users. For more information, see Message format and transmission in Exchange Online.

Other 5.0.350 errors

Typically, there's nothing that support can do for you, since the problem lies with the recipient's email system.

The Diagnostic information for administrators section in the bounce message will contain the original error message when Microsoft 365 or Office 365 tried to send the message to the external email server or service. Use this information to help identify the issue, and to see if there's anything you can do to fix the problem.

If you want to install and run more than one version of Microsoft 365 on the same PC, here are some tips to help you avoid most set up errors:

Note: If not otherwise stated, the following statements also apply to individual apps such as Visio and Project.

• If you have a Microsoft 365 subscription or non-subscription version such as Office Home and Business 2021, 2019, 2016 or 2013, in most cases you can't run these versions together on the same computer. There is one exception to this: If one of the two products is installed through MSI (which is common for volume licensed products), these two can run side-by-side. See How to use Office 2013 suites and programs (MSI deployment) on a computer that’s running another version of Office.
• You may see a "Stop, you should wait to install Office..." error. This can happen if you have a standalone Office application (such as Word) installed on your computer, but a newer version of the application is already included in the suite you're trying to install. In this case, the standalone version will be removed. However, if the standalone application isn’t part of the new Microsoft 365 suite you are trying to install, then the standalone application will be left on the machine and the Microsoft 365 suite will successfully install.
• Running multiple versions of Office on Windows when Remote Desktop Services (RDS) is enabled in not supported. See No support for multiple Office versions installed on a machine with Remote Desktop Service (RDS).
• Install earlier versions of Microsoft 365 first. For example, install Office 2013 before installing Office 2021, Office 2019, or Office 2016 . This also applies to other products from the Microsoft 365 family, like Visio, Project or Access Runtime as well as Language Packs and Proofing Tools. If you don't install Microsoft 365 in this order, you may have to repair the later versions of Microsoft 365 afterwards.
• Make sure all versions of Microsoft 365 are either 32-bit or 64-bit. You can’t have a mix of both. See “Office (64-bit or 32-bit) couldn’t be installed” error when trying to install.

Keep in mind that even if you follow these recommendations, you might still run into issues when you use two versions of Microsoft 365 on the same PC. If you decide not to keep both versions and you uninstall the earlier version, you might need to repair the version remaining to make sure that the file associations will work correctly.

Related Topics

"Stop, you should wait to install Office 2016" error Office installed with Click-to-Run and Windows Installer on same computer isn't supported Information about how to use Office 2013 suites and programs (MSI deployment) on a computer running another version of Office

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.