We are still reciving an exorband amount of SPAM in our end users inboxes, most of which is obvious SPAM. We did get an update on our support request for blocking TLD's. The instructions provided have worked, and are as follows
Create new policy under "Additional Policy"
Under "Select Users" option, choose "Include Sender" tab
Under "Custom Groups" add **@**.domain_you_wish_to_block (*Note you can add multiple entries)
This has largely done the job for us, but we are still watching inbound mail and blocking the spammy TLD's. We do use some judgement on blocking, but it is simpler at this point to shoot first and ask questions later due to the sheer volume of unwanted content coming in.
It would be nice if Sophos would code in the ablity to use custom DNSBL or SURBL resources, as it would allow the customer to be as agressive as they would like. Most of the public SURBL's are already updated, and are able to block the content that is coming in, but choosing the list is not a one size fits all solution.
We are still reciving an exorband amount of SPAM in our end users inboxes, most of which is obvious SPAM. We did get an update on our support request for blocking TLD's. The instructions provided have worked, and are as follows
Create new policy under "Additional Policy"
Under "Select Users" option, choose "Include Sender" tab
Under "Custom Groups" add **@**.domain_you_wish_to_block (*Note you can add multiple entries)
This has largely done the job for us, but we are still watching inbound mail and blocking the spammy TLD's. We do use some judgement on blocking, but it is simpler at this point to shoot first and ask questions later due to the sheer volume of unwanted content coming in.
It would be nice if Sophos would code in the ablity to use custom DNSBL or SURBL resources, as it would allow the customer to be as agressive as they would like. Most of the public SURBL's are already updated, and are able to block the content that is coming in, but choosing the list is not a one size fits all solution.