Answer

PROBLEM

The mail monitoring rules do not monitor emails sent from or to the GFI MailEssentials administrator (specified under the General Properties) and the email address to which the monitored emails are being sent to. They might also not be monitoring emails for regular users as well.

ENVIRONMENT

• GFI MailEssentials
• All supported environments

SOLUTION

If this is pertaining to inbound external emails, close and re-open the GFI MailEssentials configuration console after saving the changes. If this is pertaining to internal-to-internal emails, please note that mail monitoring rules will not work for emails sent between internal users of the same information store.

If no email copies are being delivered at all, this may be due to a missing information in the config.mdb in regard to the specified directory path of the Pickup folder. Open the config.mdb (Database location  ...GFI\MailEssentials\Antispam\Config.mdb) and check the tb_general table to ensure the Pickup path is properly defined. Mail Monitoring will not be able to deliver to the recipient folder otherwise. 

1. Gather a copy of the customers config.mdb (Database location  ...GFI\MailEssentials\Antispam\Config.mdb)
2. Open the database using Microsoft Access and navigate to the tb_general table
3. Verify that the correct Exchange pickup paths are located in the table (Remove blank tables if they are listed below the actual pickup path)
4. Replace the config.mdb with your current database by doing the following steps
5. Stop the smtp service or Microsoft Transport service
6. Stop all MailEssentials services taking note of any dependencies
7. Navigate to the MailEssentials installation directory and find a file called config.mdb (C:\Program Files (x86)\GFI\MailEssentials\Antispam)
8. Rename config.mdb to old_config.mdb
9. Drop the edited config.mdb that you added the pickup paths in access into the above location
10. Restart all services from steps 1 and 2
11. If the monitoring rules still do not apply, contact support.

If the monitoring rules still do not apply, contact support.

CAUSE

The config.mdb is unable to update for some fields until the configuration console is closed and the service is able to update the file.