Allow Wildcard Support for Email Domain Filtering
Would be very helpful to be able to create content scanning rule using wildcard to filter known spam/spoofed email top-level-domains.
Filter rules using .xyz, .dot, etc. instead of domain1.xyz, domain2.xyz, domain3.xyz, etc.
What we really need is the ability to really use wildcards such as *@*.icu and *@*.xyz not just *@blah.icu
We get a ton of spam from these and the block only accepts formats like the last example above.
Our mail server will block those type of wildcard expressions but the Sophos XG will not.
So, what happens is the users now get huge quarantine reports from Sophos where before the mail server would block the email.
The only solution at present is to turn off Spam filtering on the XG which kind of defeats the reason for using it in the first place.
Christian Krenn commented
Bruce Dubbink commented
This is nuts! I saw in another conversation where Alan Toews said, "This feature is planned for XG V17" regarding use of wildcards for subdomains.
I believe I am now on 17.0.5.... Are you kidding me?
has this still not been fixed?
This is seriously a BASIC necessity i dont understand how a wildcard on a UTM can't be used.
This is almost a deal breaker in some scenarios. Example, filtering internet, but needing to allow stuff like, Airwatch and google app management.
They consistently just jump from subdomain as a cluster.
it nearly impossible to actually give all addresses in a whitelist.
Todd Carpenter commented
This also needs to include firewall rules as its currently not possible to bypass traffic for applications that rely on random subdomains.
One of our customer is looking for Allow wildcard support for email domain filtering which is mandatory for them.
Need your immediate support and fix for the same.