Notification emails from Veeam Backup for Microsoft 365 are sent in an unexpected language

KB ID: 2692
Product: Veeam Backup for Microsoft 365
Published: 2018-07-24
Last Modified: 2021-07-14
Languages: FR
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

Email notifications sent by Veeam Backup for Microsoft 365 are illegible or unexpectedly contain Chinese characters.

notification

Cause

The issue is caused by an encoding conflict. By default, Veeam Backup for Microsoft 365 uses UTF-16 character encoding, and the issue appears under following circumstances:

  • Use of Mimecast or Thunderbird
  • Office 365 organization located in Microsoft Azure China or Germany regions.

Solution

Email notification encoding can be changed in Veeam Backup for Microsoft 365. Depending on whether this is a test notification or not, an email will be sent by Veeam Backup for Microsoft 365 Service or Veeam Backup for Microsoft 365 Proxy service respectively.

To change email notifications encoding, do the following:

  1. Ensure no backup jobs are running
  2. Stop Veeam Backup for Microsoft 365 Service
  3. Stop Veeam Backup for Microsoft 365 Proxy service
  4. Navigate to C:\ProgramData\Veeam\Backup365
  5. To change encoding for test emails, edit Config.xml file by adding the following line between <Veeam> and <Arсhiver>:
    <Email MessageHeadersEncoding="UTF-8" MessageSubjectEncoding="UTF-8" MessageBodyEncoding="UTF-8" />
    
    config.xml
  6. To change encoding for email notifications sent by a backup job, edit Proxy.xml file by adding the same line there:
    proxy.xml
  7. Start Veeam Backup for Microsoft 365 Proxy service
  8. Start Veeam Backup for Microsoft 365 Service
  9. If you have any remote proxies, repeat steps 1, 3, 4 and 6 for each remote proxy.

More Information

A similar issue may occur with Veeam Explorer for Microsoft Exchange and is documented in https://www.veeam.com/kb4188.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.