MailStore Server Help - Pages with pending changes [en]

System Requirements

2026-02-20T12:12:34Z

Implementation

2026-02-20T12:23:36Z

Template:Hosted Exchange Versions

2026-02-20T12:26:41Z

Archiving Emails from Microsoft 365 Hybrid

2026-02-20T12:35:10Z

Archiving Emails from Microsoft Exchange 2016

2026-02-20T12:40:23Z

Archiving Emails from Microsoft Exchange 2019

2026-02-20T12:40:44Z

Synchronizing User Accounts with Microsoft 365 - Modern Authentication

2026-03-19T12:47:34Z

Configuring API Permissions in Microsoft Entra ID

Exporting Email

2026-03-23T10:45:37Z

HelpTopicIds

2026-03-24T10:04:00Z

MailStore Help

2026-03-26T08:41:37Z

EWS Migration

2026-04-08T15:00:49Z

MailStore Server Management Shell

2026-04-09T09:59:27Z

Client side commands

@@ Line 18: / Line 18: @@
 * Microsoft Windows 11
 * Microsoft Windows Server 2025 (Essentials, Standard, Datacenter, Datacenter Azure Edition)
 * Microsoft Windows Server 2022 (Essentials, Standard, Datacenter, Datacenter Azure Edition)
@@ Line 40: / Line 39: @@
 * Microsoft Outlook 2024 (Click-to-Run only, Windows Store version is '''not''' supported)
 * Microsoft Outlook 2021 (Click-to-Run only, Windows Store version is '''not''' supported)
-{{Multiline_Notices|Heading=Important Notice|{{3rd_Party_Product_EOL_Notice|Outlook 2003, 2007, 2010 and 2013|Microsoft|are}}}}
+{{Multiline_Notices|Heading=Important Notice|{{3rd_Party_Product_EOL_Notice|Outlook 2003, 2007, 2010, 2013, 2016 and 2019|Microsoft}}}}
 ==== MailStore Outlook App ====
@@ Line 72: / Line 68: @@
 |-
 ! Windows 11
 | style="text-align: center; | Supported
 | style="text-align: center; | Supported
 | style="text-align: center; | Supported
 |-
 ! macOS

@@ Line 4: / Line 4: @@
 * [[Archiving Emails from Microsoft 365 Hybrid|Microsoft Exchange Online / Microsoft 365 Hybrid]]
 * [[Archiving Emails from Microsoft Exchange SE|Microsoft Exchange SE]]
 * [[Archiving Emails from Outlook.com|Outlook.com (Hotmail, Live, MSN)]]
 ==== Google Workspace & Gmail ====
@@ Line 24: / Line 22: @@
 ==== Legacy Implementation Guides ====
 {{{1|}}}
 * [[Archiving Emails from Microsoft Exchange 2013|Microsoft Exchange 2013]]
 * [[Archiving Emails from Microsoft Exchange 2010|Microsoft Exchange 2010]]

@@ Line 1: / Line 1: @@
 * [[Archiving_Emails_from_Microsoft_Exchange_SE#{{{1|}}}|{{{2|Microsoft Exchange}}} SE]]
 <noinclude>
 [[de:Vorlage:Hosted_Exchange_Versionen]]
 [[en:Template:Hosted_Exchange_Versions]]
 <noinclude>

@@ Line 37: / Line 37: @@
 * Then configure your local Exchange Server to also send their journal reports to the same Gateway mailbox. Use the manual for your matching Exchange Server version, but we recommend not creating a journal mailbox (skip step 1 in this case), but to define the external email address of your MailStore Gateway to be the recipient of these reports. This way, all reports are received at the same destination:
 ** [[Archiving_Emails_from_Microsoft_Exchange_SE#Archiving_Incoming_and_Outgoing_Emails_Directly|Exchange SE]]
-** [[Archiving_Emails_from_Microsoft_Exchange_2019#Archiving_Incoming_and_Outgoing_Emails_Directly|Exchange 2019]]
+** [[Archiving_Emails_from_Microsoft_Exchange_2019#Archiving_Incoming_and_Outgoing_Emails_Directly|Exchange 2019 (Legacy System)]]
-** [[Archiving_Emails_from_Microsoft_Exchange_2016#Archiving_Incoming_and_Outgoing_Emails_Directly|Exchange 2016]]
+** [[Archiving_Emails_from_Microsoft_Exchange_2016#Archiving_Incoming_and_Outgoing_Emails_Directly|Exchange 2016 (Legacy System)]]
 ** [[Archiving_Emails_from_Microsoft_Exchange_2013#Archiving_Incoming_and_Outgoing_Emails_Directly|Exchange 2013 (Legacy System)]]

← Older revision		Revision as of 12:40, 20 February 2026
Line 1:		Line 1:
		+	{{Multiline_Notices\|Heading=Important Notice\|{{3rd_Party_Product_EOL_Notice\|Exchange 2016\|Microsoft}}}}
		+
		+
	{{Implementation Guide Preamble\|Microsoft Exchange 2016}}		{{Implementation Guide Preamble\|Microsoft Exchange 2016}}

@@ Line 114: / Line 114: @@
 * Enable the ''full_access_as_app'' permission in the ''Select permissions'' section.
 * '''New in 25.3''': Also enable the permission ''SMTP.SendAsApp'' in the ''SMTP'' section.
 * Click on ''Add permissions''.
-* The permissions are updated and the ''full_access_as_app'' and ''SMTP.SendAsApp'' permissions appear in the API permissions list under ''Exchange''.
+* The permissions are updated and the ''full_access_as_app'', ''SMTP.SendAsApp''  and ''IMAP.AccessAsApp'' permissions appear in the API permissions list under ''Exchange''.
 * Now click on the ''Grant admin consent for <your tenant name>'' button in the ''Configured permissions'' section.
 * Acknowledge the following notice with ''Yes''.
@@ Line 128: / Line 129: @@
 *'''Synchronize enabled users only'''<br/>Only Microsoft 365 user accounts that do not have their login to Microsoft 365 blocked will be taken into account by the synchronization.
 *'''Sync only these groups'''<br/>Choose one or several Microsoft 365 security groups if you only want their members to be created as MailStore Server users. That way it's possible to exclude certain users from being synchronized to MailStore Server.
 {{Directory Services Options|Microsoft 365 tenant}}

@@ Line 6: / Line 6: @@
 === Email Server ===
 *'''Microsoft&nbsp;365 Mailbox''' - A folder named ''MailStore Export'' is created in the Microsoft&nbsp;365 mailbox into which emails are copied. If the option ''Retain folder structure'' is checked, the archive's folder hierarchy will be created in the destination, otherwise all email will be stored in the same folder.
 *'''Exchange Mailbox''' - A folder named ''MailStore Export'' is created in the Exchange mailbox into which emails are copied. If the option ''Retain folder structure'' is checked, the archive's folder hierarchy will be created in the destination, otherwise all email will be stored in the same folder.
 *'''Google Workspace''' - A folder named ''MailStore Export'' is created in a Google Workspace mailbox into which emails are copied.

@@ Line 9: / Line 9: @@
 * arch_filepst - [[Archiving_Outlook_PST_Files_Directly]]
 * arch_gateway - [[Archiving_MailStore_Gateway_Mailbox]]
 * arch_nospamproxy - [[Archiving_Emails_from_NoSpamProxy]]
 * gateway_introduction - [[Archiving_MailStore_Gateway_Mailbox]]
@@ Line 106: / 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 63: / Line 63: @@
 ==== Knowledge base ====
 * [[EWS Error Codes]]
 * [[Flagged Emails]]
 * [[Message Date of an Email]]
 * [[Email encryption in Microsoft 365]]
 |-
 | valign="top" width="50%" |

@@ 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]]

@@ 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