After configuring all post-install actions, MailEssentials is usually ready to start protecting and filtering your mail system from malicious and spam emails.
If for any reason this does not happen and there are no obvious pointers from the debug logs or the Configuration UI, this article provides a methodology and tools that can be utilized to test MailEssentials by looking at some of the general settings and filters that can be tweaked to restore mail flow.
The best way to test whether MailEssentials is blocking unwanted Emails as expected is by sending inbound and outbound test emails that are purposely composed in such a way that they will be blocked by the various MailEssentials Anti-Spam and Email Security modules.
You will require the following to execute the various troubleshooting tests in a controlled environment:
- An SMTP client (such as KMail or Microsoft Outlook) connected to your SMTP server or Exchange environment for sending the test emails.
- Some of the tests require administrative access to a local DNS server for the creation of the test DNS records and MailEssentials to be configured to use this local DNS for name resolution.
Follow the linked articles below for step by step instructions on how to test various MailEssentials features that can be affected by the wrong configuration in the General Settings:
- How to test IP DNS Blocklist
- How to test URI DNS Blocklist
- Header Checking - Character Sets
- Configuring supported security protocols
- Testing MailEssentials Anti-Virus Engines
- Configuring Bayesian Filter tokens update period