Forum Discussion

ArjanBroekhuizen's avatar
ArjanBroekhuizen
Brass Contributor
Mar 21, 2025
Solved

Exchange Online recipient limits

Hello all,

For one of our user I get the notification: "User xxxx has sent 999 internal and 0 external recipients in the last day, exceeding their Internal limit."

I have found this article on the Microsoft website, about "Recipient rate limit" and "Recipient limit". It is not totally clear to me what the difference is between both limit. I think the Recipient rate limit is the numbers of messages a user can send in 24 hours. The recipient limit is the limit for recipients in one mail-message.
If that is correct, I don't understand the notification we get for the user. The user has send many messages in 24 hours, but the recipient rate limt should be 10,000. The notification says 999 recipients. But that limit is for recipients in one message.

 

Or is there another limit in place that is blocking the user?

Kind regards,
Arjan

  • Finally found it. It is not in Exchange Online, but in Defender. The Anti-spam outbound policy is limiting the number of internal messages per hour.

    Now looking for a solution; spliting the number of mails over several days or modify  the anti-spam policy...

  • Schnittlauch's avatar
    Schnittlauch
    Steel Contributor

    Hi there,

     

    looks like its related to antispam policies.

    Have you checked out https://security.microsoft.com/antispam

    Choose "Anti-Spam Outbound Policy" (if you didnt create an own one).

    Edit the policy and you'll see internal rate limits.

    Eventually you'll need security administrator to edit.

    BR Schnittlauch

     

    Edit: was a few seconds too late :(

     

  • Finally found it. It is not in Exchange Online, but in Defender. The Anti-spam outbound policy is limiting the number of internal messages per hour.

    Now looking for a solution; spliting the number of mails over several days or modify  the anti-spam policy...

  • Just found that the recipient limit for this mailbox is 500. So, this limit is not causing the problem.

Resources