Exchange Online’s EWS access policy is blocking Mailmeteor
If replies to your Outlook or Microsoft 365 campaigns aren’t being detected, your organization may have an older Exchange Online security setting — the EWS application access policy — turned on without Mailmeteor added to it. Despite its name, this policy also filters the Microsoft Graph API traffic Mailmeteor uses, so it can silently block Mailmeteor even though we don’t use EWS at all. Below is how to recognize it and how your admin can fix it in a couple of PowerShell commands.
Symptoms
You may be affected if, when sending from an Outlook / Microsoft 365 sender account:
- Replies to your campaign aren’t marked as replied in the Mailmeteor Dashboard, even though the recipient did reply.
- A scheduled follow-up email is sent to a recipient who already replied to the original email.
- Other Outlook-dependent features in Mailmeteor (for example, bounce or reply-based automations) don’t seem to pick up activity that you can see in Outlook itself.
This typically affects only Outlook/Microsoft 365 senders, and often only some senders in your organization — for example, if the policy was configured for one mailbox rather than the whole tenant.
Why this happens
Mailmeteor’s Outlook integration (including reply detection) uses the Microsoft Graph API. We don’t use Exchange Web Services (EWS).
However, Exchange Online has an older access-control setting called EwsApplicationAccessPolicy, together with an EwsAllowList and an EwsBlockList. It was originally built to restrict EWS clients by their user agent string, but Microsoft’s documentation confirms it also applies to Microsoft Graph and REST requests that access a mailbox.
In other words: if this policy is set to only allow specific apps (or to block specific apps) by user agent, and Mailmeteor isn’t on the right list, Exchange will reject Mailmeteor’s Graph requests to the mailbox with an access-denied error.
The policy can be set for the whole organization, or for an individual mailbox. A mailbox-level setting can apply to that user even when nothing is configured at the organization level, so both should be checked.
How to check if this is the cause
Ask your Exchange Online / Microsoft 365 administrator to run these two checks in Exchange Online PowerShell.
How to fix it
Mailmeteor’s user agent is:
Mailmeteor/1.0 (+https://mailmeteor.com)
EwsAllowList and EwsBlockList support wildcards, so we recommend using Mailmeteor/* rather than the exact string above — it keeps working if our version number ever changes.
Use the @{Add=...} / @{Remove=...} syntax below, not a plain assignment. A plain assignment (e.g. -EwsAllowList "Mailmeteor/*") replaces the entire list, which would remove every other app your organization already allowed or blocked.
About the EWS retirement
Microsoft is separately retiring Exchange Web Services (EWS) itself, with a newer, unrelated control called EwsAllowedAppIDs. Here’s how that relates to Mailmeteor:
Does the EWS retirement affect Mailmeteor? No. Mailmeteor’s Outlook integration uses Microsoft Graph, not EWS, so it isn’t part of what’s being retired.
Do I need to reconnect my Outlook account because of this? No, nothing changes on your end.
Do I need to add Mailmeteor to EwsAllowedAppIDs?
No. EwsAllowedAppIDs is an application-ID-based allow list that only controls EWS access. It’s a different mechanism from EwsAllowList/EwsBlockList, and it doesn’t apply to Mailmeteor.
If our admin is cleaning up old EWS settings after the retirement, can we remove Mailmeteor’s EwsAllowList entry?
No — please keep it. Microsoft’s documentation confirms the user-agent-based EwsAllowList/EwsBlockList policy keeps affecting Microsoft Graph/REST traffic even once EWS itself is gone, so removing Mailmeteor’s entry could silently break reply detection again.
How to confirm it’s fixed
Once the allow/block list change has had time to propagate:
- Send yourself a test campaign from the Mailmeteor Dashboard.
- Reply to the email you receive.
- Check the campaign in Mailmeteor — the recipient should now show as replied.
- If the campaign includes a follow-up step, confirm it doesn’t get sent to you after your reply.
Still blocked?
If reply detection still isn’t working after updating the allow/block list and waiting for the change to take effect, contact our support team and include:
- The output of both PowerShell commands from How to check if this is the cause
- The Outlook/Microsoft 365 sender address affected
- When the allow/block list change was made
We’ll be happy to help you resolve it quickly.