MailStore Server Help - Recent changes [en]

Graph API Error Codes

Cstelzmann — Thu, 09 Apr 2026 12:18:48 GMT

text does not support structured data

EWS Migration

Ltalaschus — Thu, 09 Apr 2026 10:19:19 GMT

EWS Migration

Rjansen — Thu, 09 Apr 2026 10:13:01 GMT

MailStore Server Management Shell

Ltalaschus — Thu, 09 Apr 2026 09:59:27 GMT

Client side commands

MailStore Help

Ltalaschus — Thu, 09 Apr 2026 09:55:03 GMT

HelpTopicIds

Ltalaschus — Thu, 09 Apr 2026 09:48:20 GMT

Graph API Error Codes

Ltalaschus — Thu, 09 Apr 2026 09:46:16 GMT

Graph API Error Codes

Ltalaschus — Thu, 09 Apr 2026 09:24:14 GMT

Created page with "== ErrorMimeContentConversionFailed == '''Problem:''' While archiving email from a Microsoft Exchange server an EWS error code ErrorMimeContentConversionFailed occurs. '''Sol..."

New page

== ErrorMimeContentConversionFailed ==
'''Problem:''' While archiving email from a Microsoft Exchange server an EWS error code ErrorMimeContentConversionFailed occurs.

'''Solution:''' This kind of Exchange internal server error is caused by an internal Exchange function that is not able to convert a message from Exchange's internal MAPI format into the RFC822 compliant MIME format which is also used by MailStore Server. In nearly all cases the original MIME message received by the Exchange server already contained invalid data, such as an appointment request confirmation without references to the original appointment. Therefore it is usually safe to delete those emails.

Due to that error, the archiving profile itself terminates with a non-successful status code. This behavior can be changed since MailStore Server 8 by modifying the global property public.arcclient.skipMimeContentConversionFailed by executing the following command in [[MailStore_Server_Management_Shell|MailStore's Management Shell]]:

store-setprop --name="public.arcclient.skipMimeContentConversionFailed" --value="true"

'''Please note:''' Independent of this global property, MailStore Server is neither able to archive messages where the above error occurred nor delete them from the Exchange server.

[[de:Graph_API-Fehlermeldungen]]
[[en:Graph_API_Error_Codes]]

Microsoft 365 Profile Conversion Tool

Ltalaschus — Wed, 08 Apr 2026 15:18:48 GMT

EWS Migration

Ltalaschus — Wed, 08 Apr 2026 15:00:49 GMT

File:Ews conversion message.png

Ltalaschus — Wed, 08 Apr 2026 14:46:13 GMT

Ltalaschus uploaded File:Ews conversion message.png

New page

@@ Line 1: / Line 1: @@
 == text does not support structured data ==
-'''Problem:''' While archiving email from a Microsoft 365 server an Graph API error code ''text does not support structured data'' occurs.
+'''Problem:''' While archiving email from Microsoft 365 a Graph API error code ''text does not support structured data'' occurs.
 '''Solution:''' This kind of server error is caused by an internal Microsoft 365 function that is not able to convert a message from its internal format into the RFC822 compliant MIME format which is also used by MailStore Server. In nearly all cases the original MIME message received by the mail server already contained invalid data, such as an appointment request confirmation without references to the original appointment. Therefore it is usually safe to delete those emails.

@@ Line 34: / Line 34: @@
 ==== June 2026 ====
-If you are an Exchange Online Kiosk, Microsoft Office 365, or Office 365 F1/F3 customer, all profiles must be migrated to Graph API and IMAP.
+If you are an Exchange Online Kiosk, Microsoft Office 365, or Office 365 F1/F3 customer, all profiles [https://techcommunity.microsoft.com/blog/exchange/update-to-ews-access-for-kiosk--frontline-worker-licensed-users/4474299 must be migrated] to Graph API and IMAP.
-Archiving Exchange Online archive mailboxes and Exchange Online Public Folders will [https://techcommunity.microsoft.com/blog/exchange/update-to-ews-access-for-kiosk--frontline-worker-licensed-users/4474299 no longer be possible].
+Archiving Exchange Online archive mailboxes and Exchange Online Public Folders will no longer be possible.
 ==== October 2026 ====

@@ Line 36: / Line 36: @@
 If you are an Exchange Online Kiosk, Microsoft Office 365, or Office 365 F1/F3 customer, all profiles must be migrated to Graph API and IMAP.
-Archiving Exchange Online archive mailboxes and Exchange Online Public Folders will no longer be possible.
+Archiving Exchange Online archive mailboxes and Exchange Online Public Folders will [https://techcommunity.microsoft.com/blog/exchange/update-to-ews-access-for-kiosk--frontline-worker-licensed-users/4474299 no longer be possible].
 ==== October 2026 ====

@@ Line 148: / Line 148: @@
 ! scope="col" bgcolor="#cccccc" | Values
 ! scope="col" bgcolor="#cccccc" | Default
 |-
 | scope="col" width="20%" align="left" valign="top" | public.arcclient.skipMimeContentConversionFailed

@@ Line 63: / Line 63: @@
 ==== Knowledge base ====
 * [[EWS Error Codes]]
 * [[Flagged Emails]]
 * [[Message Date of an Email]]

@@ Line 107: / Line 107: @@
 * cred_microsoft365 - [[Synchronizing_User_Accounts_with_Microsoft_365_(Modern_Authentication)#Creating_Credentials_in_MailStore_Server]]
 * expo_mailstorecloudbulk - [[MailStore_Cloud_Help#Migration_from_MailStore_Server_to_MailStore_Cloud]]
+* graphmimeconversionfailed - [[Graph_API_Error_Codes]]
 [[de:HelpTopicIds]]
 [[en:helpTopicIds]]

@@ Line 1: / Line 1: @@
-== ErrorMimeContentConversionFailed ==
+== text does not support structured data ==
-'''Problem:''' While archiving email from a Microsoft Exchange server an EWS error code ErrorMimeContentConversionFailed occurs.
+'''Problem:''' While archiving email from a Microsoft 365 server an Graph API error code ''text does not support structured data'' occurs.
-'''Solution:''' This kind of Exchange internal server error is caused by an internal Exchange function that is not able to convert a message from Exchange's internal MAPI format into the RFC822 compliant MIME format which is also used by MailStore Server. In nearly all cases the original MIME message received by the Exchange server already contained invalid data, such as an appointment request confirmation without references to the original appointment. Therefore it is usually safe to delete those emails.
+'''Solution:''' This kind of server error is caused by an internal Microsoft 365 function that is not able to convert a message from its internal format into the RFC822 compliant MIME format which is also used by MailStore Server. In nearly all cases the original MIME message received by the mail server already contained invalid data, such as an appointment request confirmation without references to the original appointment. Therefore it is usually safe to delete those emails.
-Due to that error, the archiving profile itself terminates with a non-successful status code. This behavior can be changed since MailStore Server 8 by modifying the global property public.arcclient.skipMimeContentConversionFailed by executing the following command in [[MailStore_Server_Management_Shell|MailStore's Management Shell]]:
+Due to that error, the archiving profile itself terminates with a non-successful status code. This behavior can be changed by modifying the global property ''public.arcclient.skipGraphContentConversionFailed'' by executing the following command in [[MailStore_Server_Management_Shell|MailStore's Management Shell]]:
-  store-setprop --name="public.arcclient.skipMimeContentConversionFailed" --value="true"
+  store-setprop --name="public.arcclient.skipGraphContentConversionFailed" --value="true"
-'''Please note:''' Independent of this global property, MailStore Server is neither able to archive messages where the above error occurred nor delete them from the Exchange server.
+'''Please note:''' Independent of this global property, MailStore Server is neither able to archive messages where the above error occurred nor delete them from the mail server.
 [[de:Graph_API-Fehlermeldungen]]
 [[en:Graph_API_Error_Codes]]

@@ Line 1: / Line 1: @@
-Microsoft is planning to [https://techcommunity.microsoft.com/blog/exchange/retirement-of-exchange-web-services-in-exchange-online/3924440 retire] the Exchange Web Service(EWS) protocol in Exchange Online. This decision affects all companies that use EWS not just MailStore. This makes it necessary to use alternative access to Exchange Online mailboxes going into the future. We provide a conversion tool that will try to help you migrating profiles that rely on EWS and will stop working in the future.
+Microsoft is planning to retire the Exchange Web Service(EWS) protocol in Exchange Online. This decision affects all companies that use EWS not just MailStore. This makes it necessary to use alternative access to Exchange Online mailboxes going into the future. Further details about the proposed discontinuation of the EWS protocol can be found in the [[EWS Migration|migration article]].
-Further details about the proposed discontinuation of the EWS protocol can be found in the [[EWS Migration]] article or you might want to follow our [https://www.mailstore.com/en/blog/microsoft-is-discontinuing-ews-for-m365/ blog].
+We provide a conversion tool that will try to help you migrating profiles that rely on EWS and will stop working in the future.
 ===Accessing the conversion tool===
-When your MailStore Server installation is using a MIcrosoft 365 profile you should see a warning message on your dashboard. Click on that will open the Microsoft 365 Profile Conversion tool.
+When your MailStore Server installation is using a Microsoft 365 profile you should see a warning message on your dashboard. Click on that will open the Microsoft 365 Profile Conversion tool.
 [[File:ConversionTool_en.png]]
@@ Line 16: / Line 15: @@
 * <b>not supported</b>
 *; Those profiles can't be supported anymore when EWS is disabled. Microsoft did not provide alternatives yet without the use of EWS.
-** <b>Public Folders</b> access will no longer be supported by Microsoft. Microsoft recommends a [https://learn.microsoft.com/en-us/exchange/collaboration/public-folders/migrate-to-microsoft-365-groups| migration] to  Microsoft 365 Groups
+** <b>Public Folders</b> access will no longer be supported by Microsoft.
-** <b>Archive mailboxes</b> or sometimes called In-Place Archives are currently only supported via EWS. A future solution has been [https://techcommunity.microsoft.com/blog/exchange/retirement-of-exchange-web-services-in-exchange-online/3924440| hinted] by Microsoft. But no actual plan has been released yet.
+** <b>Archive mailboxes</b> or sometimes called In-Place Archives are currently only supported via EWS.
 * <b>not needed</b>
 *;Those profiles are either already converted or has been created currently with a EWS replacement solution already. Those profile can be considered safe and are shown here for completeness.

@@ Line 1: / Line 1: @@
-== Microsoft Is Discontinuing Its Exchange Web Services (EWS) for Microsoft 365 ==
+__NOTOC__
-Microsoft [https://techcommunity.microsoft.com/blog/exchange/retirement-of-exchange-web-services-in-exchange-online/3924440 has announced] that it will no longer support Exchange Web Services (EWS) for Exchange Online as of October 1, 2026. This decision affects all companies that use EWS in combination with Exchange Online (Microsoft 365).
+Exchange Web Services (EWS) is a technology that was developed specifically for accessing Exchange data. The API enables access to data from Microsoft Exchange Server and Exchange Online, including emails and mailboxes. EWS has been a central interface for third-party solutions such as archiving systems.
-EWS is a technology that was developed specifically for accessing Exchange data. The API enables access to data from Microsoft Exchange Server and Exchange Online, including emails and mailboxes. EWS has been a central interface for third-party solutions such as archiving systems.
+== Microsoft is discontinuing Exchange Web Services (EWS) for Microsoft 365 ==
-What Will Happen in October?
+Microsoft will [https://techcommunity.microsoft.com/blog/exchange/exchange-online-ews-your-time-is-almost-up/4492361 preconfigure and potentially restrict access] to EWS based on usage starting in August 2026. Administrators can also [https://learn.microsoft.com/en-us/exchange/client-developer/exchange-web-services/how-to-control-access-to-ews-in-exchange manage the settings themselves].
-Please note: If you use Exchange Online Kiosk, Microsoft Office 365, and Office 365 F1/F3, you should make the change by June. Further information can be found [https://techcommunity.microsoft.com/blog/exchange/update-to-ews-access-for-kiosk--frontline-worker-licensed-users/4474299 here].
+For customers using Exchange Online Kiosk, Microsoft Office 365, and Office 365 F1/F3,  [https://techcommunity.microsoft.com/blog/exchange/update-to-ews-access-for-kiosk--frontline-worker-licensed-users/4474299 Microsoft will disable EWS access as early as June 2026].
-== What Will Change for MailStore Server and the MailStore SPE? ==
+== What will change for MailStore Server and MailStore SPE? ==
-The shutdown of EWS initiated by Microsoft will require adjustments to MailStore Server and the MailStore SPE, depending on your archiving strategy.
+The shutdown of EWS initiated by Microsoft will require adjustments in MailStore Server and MailStore SPE, depending on the archiving strategy. Archiving methods within MailStore Server and MailStore SPE that previously have used EWS may no longer be able to connect after October 1st and will then encounter errors.
-The following profiles are expected to be affected from October onwards, Graph API does not expose access to these and support is effectifely dropped:
+== Which protocols does MailStore use? ==
-* Importing Exchange Online archive mailboxes
+Up to and including version 25.4, MailStore exclusively created Microsoft 365 archiving and export profiles that used EWS. Starting with version 26.1, new archiving profiles for regular mailboxes use the Graph API. New archiving profiles for archive mailboxes and public folders continue to use EWS, as these are not accessible via the Graph API. New export profiles, starting with version 26.2, use the IMAP protocol, since importing complete emails into a Microsoft 365 mailbox using the Graph API is also not possible.
-Regular Exchange Online Mailboxes and Shared Mailboxes are available using Graph API. New [[Archiving_Emails_from_Microsoft_365_-_Modern_Authentication|mailbox archiving profiles]] in MailStore will use Graph API starting with version 26.1.
+=== How can MailStore support me during the migration? ===
-The [[Email_Archiving_with_MailStore_Basics|summary panel]] of the archiving or export profile tells which protocol is used. Microsoft 365 Journal archiving profiles do not typically use EWS and are therefore not affected.
+Make sure you have completed the app registration in Entra ID [[Synchronizing_User_Accounts_with_Microsoft_365_-_Modern_Authentication#Configuring_API_Permissions_in_Microsoft_Entra_ID|according to our instructions]]. In particular, the Mail.ReadWrite and IMAP.AccessAsApp permissions are now required.
 [[de:EWS Migration]]
 [[en:EWS Migration]]