Lately, we've been hit with some whaling attempts that have gotten past Mimecast. The attempts are sloppy enough to slip right past impersonation detection as they don't include anything in their message that would trigger the filter. They didn't disguise the address or attempt to make it look like our domain. The envelope, reply-to, and header
We are a new customer to Mimecast and have just turned on the Digest (That was the first obstacle for our company) I am really wanting to turn on the URLProtection (I have it on for my team) for an added layer of protection. Has anyone had a chance to write up some documentation that they did for their users. I am looking for a document to
Applies To...
Configuring a Content Examination Definition
Policy Definition
Scanning Options
Word Phrase Match List Parameter Details
Inbound and Outbound Settings
Journal Settings
See Also...
In order to analyze the content of emails, a Content Examination Definition is required. This is applied to a specific
After some back and forth in the discussion thread Is there a way to block TLDs?, an expanded and improved RegEx for stopping email from specified top level domains has been devised. Actually, 2 solutions were devised. Rodney Arthur devised this Regex code here: regex:
This page applies to the MSE v3.x or later.
Configuring the Microsoft Mailbox
Changing the MSE Connection Settings
Binding a Site
Binding a v4.x Site
Binding a v3.x Site
Displaying your MSE Site Configuration
The site configuration utility is used to configure and view information about your Mimecast Synchronization
