I tried to use envelope analysis ad add *.pw and it does not work. Do I need to just add a content analysis rule to block that? What is my best option to block anything from .ru or .tw, etc.?
Solved! Go to Solution.
What I've been doing is adding User Defined Header Rules, like this:
From Contains .pw>
and scoring 245 points. I've done 245 points for .eu>, and .pw>, 25 points for .in> and .ru>, and 75 points for .info>
The > symbol is critical, do not leave it off.
It works great here, dumping thousands of .eu and .pw spams a day.
Al McCann
What I've been doing is adding User Defined Header Rules, like this:
From Contains .pw>
and scoring 245 points. I've done 245 points for .eu>, and .pw>, 25 points for .in> and .ru>, and 75 points for .info>
The > symbol is critical, do not leave it off.
It works great here, dumping thousands of .eu and .pw spams a day.
Al McCann
Thanks!! Step by step on doing this. Not available thisway in 7.6.
Message was edited by: Mwilliam on 5/22/14 1:23:19 PM EDTWhy the smaller numbers for .ru and .in?
We have employees who have family in those countries. This just increases the score enough to quarantine the messages where the users can still see them, and release any personal ones.
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: