I wanted to add *@*.us to our dictionary called blocked senders which for the most part has just e-mail addresses in it.
Reason is there has been an increase in spam from a random email@example.com. To examples are firstname.lastname@example.org and email@example.com. Both have identical format with "Can't see the images in this e-mail? click here to view online., then a one liner such as "ADT Dealer Installed security system $99" then an image of an advertisement. That's all it is.
Since I can't think of any legitimate e-mail providers that have a .us at the end. I can only think of .com, .org, .edu, .gov that we would do buisness with. - I want to block firstname.lastname@example.org, Hence my trial of industry standard wildcard symbols *@*.us.
Anyway I tried adding *@*.us hoping it would take wildcards but I get an error message "One or more items were not added because they are either invalid terms, or already exist in the Dictionary with a different weight."
We will keep this in place until there is a business need to converse with a .us domain. With the high increase in spam image e-mails from .us domains, we feel this block is more beneficial at this time.
I know it's an old thread but i am facing the same issue on my Ironport so i applied the solution that you've mentioned earlier using the dictionary term [^@]+@[^@]+\.xx+, weight 1 and followed the steps that follow but i am still receiving spam emails from email@example.com
... and added this filter to our incoming mail policies.
Would this be a possible solution for your case? Why you want to do this with message filters? This drops all mails from this sender TLD/domain too. You are able to define other regex filters and exceptions via content filter.
You can either create a dictionary with the specified terms and call it in the content filter or configure the terms directly in the content filter. Both will work as expected. My mistake was applying the content filter to the wrong mail policy but now it's working perfectly except for the email format: firstname.lastname@example.org
DocumentationCode download linksGoalRequirementLimitationsSupported ISR
and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity
options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in
HA DocumentationCode download linksGoalRequirementLimitationsSupported
ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationCo...
Question I am currently unable to specify "crypto keyring" command when
configuring VPN connection on my cisco 2901 router. The following
licenses have been activated on my router :