spam filter allowed and blocked sender limit
Please remove Safe and Blocked Sender Limit. There should be an option to add unlimited allowed and blocked list sender and domains. Existing spam protection does not block most of emails.
Bikram SIngh commented
Is Microsoft forcing us to buy ATP by implementing such restriction?
Thats BAD BUSINESS strategy? Please rethink on it..
Jose Marti commented
Same here, limits are too small for production environments, and for big organizations or business.
Same, blocking lists should be bigger to make it easier to stop spam. Help us to help you! We are getting a lot of fake 365 login emails, won't be long before someone forgets and hits it.
Jeff Brotherston commented
Please do not limit blocked emails. It is difficult to find a decent spam blocker for Office 365 and thus we are forced to go through a long Junk Email folder every couple of days. If we can block these people it would help.
YOU NEED TO DO MORE TO HELP US DEAL WITH SPAM!!!!!!!!!!!!!!!!!!!
Jonathan L'Archevêque commented
Chris Looi commented
Ridiculous to have the limit. It just useless now if I can't add more in our safe sender emails in office365.
Changing the filter limit to unlimited, is very much needed in this spam world!
Safe and blocked sender limit too low. & please allow user safe send & block lists to be respected in cloud mailbox EOP?
Ankit Kashyap Baruah commented
The maximum limit to block senders in O365 spam filter policy is 1024. Is there a way to increase the limit? From what I have seen so far, it is not possible.
Every day, I look at invalid login attempts, malware, phishing scams, etc. I have to go to the connection filter and add blocks. Now, I have reached the limit. I can only add 3 -4 ranges every day. In order of wishful thinking:
1. Allow the Administrator to deny connections by Country.
2. Allow a full range not just 0 - 255. For example 18.104.22.168 - 22.214.171.124
3. Remove the limit on blocked Senders.
There should also be a way to determine if the Blocked Senders List is out of sync with the AD Hash. We've encountered that twice now.