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.
Anonymous
shared this idea
The limit you are talking about protects against large volume senders overwhelming the shared resources of our service and ensures emails are not all sent out at once for automated systems. Can you please tell us more about the problems this causes to the software that queueing and retries are not able to handle?
34 comments
-
Jrdn
commented
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.
-
Rob
commented
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).
-
Anonymous
commented
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....
-
Anonymous
commented
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?
-
Anonymous
commented
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.
-
Anonymous
commented
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.
-
Waqas
commented
It should be Administrator who would customized it, otherwise office automation solution holder will back to on premises or alternatives.
-
Rob
commented
Yes would be very helpful to have a higher limit
-
Anonymous
commented
What a ridiculously low limit to impose on any business...
-
Anonymous
commented
This limit is definitely too narrow for business use.
-
Colin Chen
commented
It's very unprofessional to limit the send rate in 30message per minute, especially when we're in a school which has to send lots of emails to students' parents.
-
Anonymous
commented
A Kulcs-Soft ügyfelek is ezt szeretnék
-
Anonymous
commented
Very important!!!!!!!
-
Anonymous
commented
This limit is definitely too narrow for business use
-
Andrew Milford-Wood
commented
This is a real surprise and so unhelpful. We have a few mailing lists (with consent) of several hundred apiece. Not a big emailer outside of this. Should allow extra mails for nominated senders in our organisation, or a whitelist system for lists. The only solutions e.g. use mailchimp, are not practical for various reasons. Besides, we'd rather do everything with one product. Fix it, please!!!