I think this is an excellent suggestion and I'm going to escalate a request to our Product Management team for further review on this. Thanks Gabriele!

We are actually implementing the ability to block countries and IP's for authentication at the system level.  The domain capabilities will stay the same and can extend beyond what the system administrator has set.

News on this?

Hi Ron!

In the latest version(s) you can find this option specific for every domain (under the "General" tab).

The issue is that there isn't the corresponding setting in the "Domain Defaults", so you can't create a default setting and propagate it...

We have many customers from different countries across Europe.

Actually, some customers use the Domain related settings to let users log-in only from the specific country (or countries)  they want, and often is different customer by customer.

The Domain Defaults setting should help us to give our customers a "semi-precompiled" list of countries that are enabled to login (maybe all the European countries or so). Every customer can then personalize it later.

If in the future this setting will be only system wide, that will be really troublesome...

Would it be possible for domain admin to still use the 'All But' option if the system admin has already set a block list?

We currently block some obvious offenders such as Russia at the system level. But now at the domain level we can only add to the list of blocked countries. It would be very useful to plenty of the domains on the server if the customer could allow only US.

In addition to supporting an option to implement blocking by country at the system level, I want to point out the documentation on this is confusing. This seems to suggest there is a setting in the Domain Defaults setting for the system admin, which there is not.

Why was this request marked as "completed" even though this option DOES NOT EXIST?

This is not completed at all!

Please let us know something...

+1

yes I don't understand either.

If I set block Authentication by country on general settings then can I customize at domain level?

It would be better if this setting is inserted in domain default with the typical propagation logic of sm

Hi all, 

We updated SmarterMail to include the ability to block authentication by country at the domain level. System Administrators can set a baseline for the countries they would like to block, and domain admins can expand on it, making it more strict to their needs. 

Domain Defaults are typically intended for settings that the Domain Admins don't have access to. These are for settings configured by the System Admin alone, and a feature like this should really be customizable by the Domain Admins themselves, which is why it was added to the Domain Settings > General area instead. Because we implemented a feature to allow Domain Admins to customize these settings, I thought it fitting to change the status to Complete.  

I partially agree.

What is described works. What is missing is the possibility to block countries in domain default

Hi Andrea, thank you for the clarification of your policy on this point.

Although I would have liked it to work differently, now at least I understand why and therefore, despite everything, for the moment I will accept this policy...