Increase 30 messages per minute limit
The 30 message per minute limit causes problems for software that needs to send out to many users. Now that we've migrated to Exchange Online our payroll system can no longer send out payslips because of this feature. Very limiting and a very low limit. It should at least be able to be configured to allow accounts to be exempted or have different limits.
Our service is designed to protect the resources and ensure that certain users will not overwhelm it and cause latency for others. This limit is in place to protect against spike sending that we wish to discourage. As such, we have no plans to change the limit for regular mailboxes.
Where possible, we encourage customers who have these requirements to seek solutions that do not send emails all at once, can make use of DLs, or use services like Dynamics or third-party services to send large volumes of emails to customers or student and parents.
However, we are thinking about alternatives we can provide to solve this issue of higher sending for automated email scenarios to address this customer need.
Alessandro Lo Valvo commented
At least this limit on GSuite is 60 :-(
More than 4 years later, no solution
Scott Paist commented
We're running into this with SSRS subscriptions. 30 per minute is ridiculously low. If I were trying to spam, I'd send 3000 per minute.
Please let admins control this limit on a per user basis.
David Lubman commented
We send out end of day shipping notifications and this limit has been causing us much trouble! Should be adjustable by admin to 100 per minute.
Please fix this!!!
Steve Sirag commented
I'm an O365 reseller.
The 30 message per minute limit has caught an elderly client of mine in a 3-hours-long black hole of tech support just because he copied 35 of his friends on an email. This is not an abusive user.
If you're going to put up warning flags on 30 messages in a minute, then greylist him for 5 minutes, and then let him send again. Obviously the 10k per day limits are designed to catch the truly abusive users, but 30 in a minute is far too harsh for users who are not technical and get blackholed for hours from normal email conversation. This is abusing the customer and causing a black eye for Office365.
I operate a small business with limited resources and budget specific guidelines. It was suggested to us that we leave the migrated server we previously used to this platform, and that we would not have problems with our processes. For an entire year, a total of 6 times, everything went smoothly. Now two days before a deadline, emails are blocked. These are not mass emails, these are customer specific that are bundled and sent with specific individual attachments, they are apparently considered bulk in their timing.
Now with two days to spare the suggestion is for me to 1) identify a third party to accommodate my needs and incur the expense of rewriting program or 2) rewrite program to stage the emails to meet the 30 per minute limitation. I have neither the time to investigate and vet a third party or the resources to have someone rewrite code in 48 hours at the accelerated fees of $250 per hour.
It is unconscionable to me how a company that sells this product to me more than a year ago with the constraints and needs clearly outlined, now has put me into this situation. Maybe it was in fine print, but if it were, I would not have accepted knowing this was a key component to our communication strategy.
Limits need to be asserted at the company level and when abuse is verified, then you can punish the customer. Why there is not a staging component to queue email for delivery, I will never figure that out.
Is this solved? how to increase or remove the limit for specific users? we are running into the same problem with our HR System sending pay slips to employee! please help
Some legitimate mailboxes that automate sending high volume emails. We send renewal reminders to our members from our website using just one mailbox - around 10k once a week. All our other mailboxes are just normal users where these rate limits make sense. Sometimes you legitimately need to send bulk mails. These business processes were developed with on premise Exchange servers - now we have moved to 365 the rate limits are a problem. Migrating this to our other email platforms e.g. Mailchimp is not practicable as we want to have a record of the sent items available in our mail system and we don't want to have to create a mailchimp subscriber for someone we are just emailing.
We have processes which use macros to trigger emails from outlook for initiation and management of tasks and sometimes given the scale, they can send over 30 messages/minute. This wasn't a problem in the on-premise Exchange days but now it's become a serious issue. I'd love to see a mailbox level setting for higher limits or even a one time change via working with support.
Many legacy business applications have very limited email configurations, due to having been built for wholly on prem infrastructure. I don't see a reason that it would be a problem for most applications if the mailbox would accept the mail and que it in the outbox until it can be sent.
This is actually affecting is most on the receive side. Some of our edge devices currently only support email reporting, and many are running jobs on a schedule which means we could have 50+ notifications at one time. The 30 messages per min is causing dropped reporting email
I would be in favor of allowing admins to increase the limit to some slightly higher limit, or adding in a "bulk" SKU of some sort to allow mailboxes to bypass the limit.
Dan Suban commented
Increase the send message limit from 30 messages per minute to admin requirement.
This is a dumb a$& limit when Outlook offers itself a mail merge function. Running the mail merge with over 30 separate email addresses usually causes problems with the 30 messages per minute limitation!!
Come on Microsoft!
Tom S commented
Microsoft is not applying the limit properly, or it's description of the limit is wrong. A 30 message per minute limit should apply the "554 5.2.0" exception to the MESSAGE, not some of the recipients for that message. Our problem is that If we send a message to several recipients and hit the limit, it may fail one or two of them but send to the rest. If I re-submit the email, it'll cause duplicates for some of the recipients (bad). If I delete the recipients that already received the message, then the other recipients will not see those on their copy of the email (also bad).
I agree... but I would agree more with granting the ability for administrators to specifically whitelist accounts that are used for bulk outbound messages. In my case, I have alerts that go off and notify a handful of people of an outage. If multiple outages occur at the same time, i hit the 30 message limit and I no longer get any messages until I realize the account has been disabled due to spam....
Any update on the 2016 stance on this? More and more people are trying to go for 100% cloud. MS is pushing for that as well today.
Doc Pratt commented
We just migrated a client from in-house Exchange to O365 Bus Prem., 95 licenses. Their application SW batches and sends 100 +/- invoices daily. They can group invoices and send multiples to each customer but some of their larger customers require individual invoices. There has been suggestions of going back to the exchange server but we may need to use a 3rd party SMTP server. Since the Try This Instead suggestion is over 3 years old, is there an updated suggestion?
To low, if you use a helpdesk ticketing system whereby it sends an email if there has been an update.
This needs to be raised even it its to 60-100 mails per minute.
We run into problems when sending out emails with our employee check stubs attached. We send it out of our Payroll software and we receive the error that there are too many emails from this sender. Then we have to wait 45 minutes to send more out, etc. This is a true hassle. If I could use a 3rd vendor, I would but it's already coming from a software program and not Outlook. It would be great if administrators could set this up by user. Probably impossible, but that would be great in my book.
JH Webb commented
SMTP Limit of 30 per minute is breaking report delivery and system notifications.
We use Citrix ShareFile for report delivery for both internal and external users. We use a fully license E2 account to log in. When reports post we need to be able to email notify about 250 users internally and externally. SMTP limit breaks this function.
Wesley Kirkland commented
I think this limit should be lowered. O365 is not meant for transnational email and they have tons of limits built in for this. Use something like SendGrid, PostMark, Mandrill, or MailGun.