Start a conversation

SPAM messages stopped being filtered because an incorrect license key being used

Overview

Suddenly, you see a significant increase in the number of spam messages that are being marked "Ok" in the dashboard and passed on to the user's Inbox. These are messages that would normally be caught by the SpamRazer, Spam Keyword Checking, and Header Checking modules.

The logs show that the AntiSpam Engines are not licensed:

2020-09-21,14:03:13,627,1,"#00007738","#00006e34","warning","ase_antispoofing","Licensing check: Not Licensed"
2020-09-21,14:02:37,321,1,"#00007738","#00006e34","warning","ase_bayesian","Licensing check: Not Licensed"
2020-09-21,10:22:42,008,1,"#00003bd0","#000062e0","warning","ase_blacklist","Licensing check: Not Licensed"
2020-09-21,13:59:58,790,1,"#00007738","#00003ac8","warning","ase_dnsbl","Licensing check: Not Licensed"

Solution

Checking the license status using the GFI MailEsseintals Configuration UI, shows that AntiSpam Engines are licensed.

Below a sample from the SpamRazer Configuration page:

SpamRazer_LicensingStatus.png

This behavior is consistent with an incorrect or corrupt license key stored in the Configuration Database.

  1. Retrieve your current license key by following the steps in the "How to find a lost license key for GFI MailEssentials?" article.
  2. Stop the Microsoft transport service or the SMTP service. Otherwise, the Attendant, Antispam, and Antivirus services will automatically restart, preventing the update of the .mdb file.
  3. Wait for a minute and then stop all the GFI MailEssentials services.
  4. Take a backup copy of the config.mdb file located at ..\GFI\Mailessentials\Antispam\
  5. After backing up the file, open the config.mdb file in Microsoft Access.
  6. Expand the Registration table and update the license key with the one you retrieved in Step 1.
  7. Save the changes.
  8. Start all the GFI MailEssentials services.
  9. Start the Microsoft transport service or the SMTP service.

Testing

After applying the correct the spam filters should resume and block emails.

If the issue still persists, please generate the troubleshooting logs as follows:

  • Make sure that you have tracing enabled.
  • Wait for at least 30 minutes to gather enough information and for the issue to be reproduced.
  • Run the troubleshooter:
    1. Start > Programs > GFI MailEssentials > Troubleshooter
    2. Follow the Log Generation Wizard for collecting the required and pertinent information.
    3. Select New Case when completing the log generation to attach the logs to a new case that will be automatically created, or open a support ticket manually and attach the logs to that ticket, so that the Support team can investigate the problem.
Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted
  3. Updated

Comments