Feature Request - Blacklist - All Protocols Blocked by Default
Problem reported by LD Calhoun - 3/31/2026 at 5:26 AM
Submitted
We have been having to add a lot of networks to our blacklist. When adding an IP/range, you have to manually turn on all the features to block. Maybe it is just our use case, but when we block a network, we want to block their access to all available protocols. Currently you have to manually turn on the sliders for all 9 services to block them all. It would make more sense on the blacklist to have all the services blocked by default, and have to turn off that particular service if you wanted to allow it. That just seems a lot more intuitive for a Blacklist function.

The suggested feature request in this case would be to have all services blocked by default when you go to add a new blacklist entry. Maybe others have ran into this as well, and hopefully it can be considered for a future update. 

Thank you,
LD Calhoun
+1
Gabriele Maoret - SERSIS Replied
+1
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)
John Quest Replied
Since we all know that we should all have all of our servers behind a firewall, if a network block is that bad, it should be blocked at the firewall and not even allowed to communicate with the email server at all.

My 2 cents.
Patrick Jeski Replied
This is the third request for this feature that I am aware of. Seems a popular request and trivially easy to implement.

Reply to Thread

Enter the verification text