Overview
This article explains the various debug logs that are created by MailEssentials, how to enable extended debugging, and the format of the debug logs.
Introduction
MailEssentials provides the facility of creating log files for debugging purposes. Use tracing for troubleshooting purposes or when contacting GFI Support.
You can enable or disable debug logging by following the steps outlined in this linked article: How can I enable or disable debug logging in GFI MailEssentials?
The next section explains the various debug logs that are created by MailEssentials, how to enable extended debugging, and the format of the debug logs.
Description
Enabling Debug logging in MailEssentials
Debug logging for all the modules in MailEssentials can be enabled from the MailEssentials Switchboard or the Windows registry.
Enabling from the Switchboard:
Start > All Programs > GFI MailEssentials > GFI MailEssentials Switchboard > Tracing Tab and Select Tracing enabled by ticking the checkbox.
From the Registry on x86 systems:
[HKEY_LOCAL_MACHINE\SOFTWARE\GFI\MailEssentials\Config]
[HKEY_LOCAL_MACHINE\SOFTWARE\GFI\MailEssentials\AntiSpam\Config]
[HKEY_LOCAL_MACHINE\SOFTWARE\GFI\MailEssentials\EmailSecurity\Config]
Set the ‘Debug’ (dword) values to ‘1’. After the ‘Debug’ value has been changed to ‘1’, the GFI MailEssentials services and the IIS Admin service will have to be restarted.
From the Registry on x64 systems:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\GFI\MailEssentials\Config]
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\GFI\MailEssentials\AntiSpam\Config]
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\GFI\MailEssentials\EmailSecurity\Config]
Set the ‘Debug’ (dword) values to ‘1’. After the ‘Debug’ value has been changed to ‘1’, the GFI MailEssentials services and the Microsoft Exchange Transport service need to be restarted.
Location of the Debug Logs
When Debugging is enabled, all the debug log files from the various MailEssentials components are saved to the following locations:
- <GFI MailEssentials installation path>\GFI\MailEssentials\DebugLogs\
- <GFI MailEssentials installation path>\GFI\MailEssentials\Antispam\DebugLogs\
- <GFI MailEssentials installation path>\GFI\MailEssentials\EmailSecurity\DebugLogs\
- <GFI MailEssentials installation path>\GFI\MailEssentials\WwwConf\DebugLogs\
- <GFI MailEssentials installation path>\GFI\MailEssentials\ActionServices\DebugLogs\
- <GFI MailEssentials installation path>\GFI\MailEssentials\Attendant\DebugLogs\
- <GFI MailEssentials installation path>\GFI\MailEssentials\Backend\DebugLogs\
Most of the debug log files have a limit of 5Mb. When this limit is reached, the log file is saved to a .bak file. When the log file reaches again 5Mb, the .bak file is replaced with a new one. Some debug log files have a limit of less than 5Mb. Others, like the MTA debug log file, has had its limit increased to 10Mb.
Format of the Debug logs
All debug logs differentiate emails using the Message-ID, so when troubleshooting a problem using the debug logs, it is important that we get an email showing the problem and that it contains the email header information. Refer to this linked article on Reading Email Headers to extract the Message-ID.
All the debug log files have the same standard format, which is shown below:
Date, Time, Millisec., Log Level, Process ID, Thread ID, Event Type, Source, Description
The following table provides an explanation of the parts (columns) that are mostly used for troubleshooting:
|
Log Level |
MailEssentials supports different logging levels, however only Log Level ‘1’ is implemented |
|
Thread ID |
This is important while troubleshooting a problem. MailEssentials can start multiple threads to process emails. Each thread can scan only one email at a time; however, each thread can scan multiple emails after each other. |
|
Event Type |
Will indicate if the line of logging is informational (info), Warning logging (warning) or an error logging (error) |
|
Source |
Will show the source of the logging – the module that is writing to the file |
|
Description |
The details of the line of logging |
All MailEssentials logs (with a few exceptions) follow the same standard format as shown in the example below:
2015-06-02,10:24:29,444,1,"#00001ce4","#00002648","info ","BitDefender Engine","CXScanner::ScanPFI, Scanning [E-Mail-Text]."
- Date – Date of the entry (Year-Month-Day)
- Time – 24 hour clock time (Hour:Minute:Second)
- Milliseconds, Log Level, Process ID, Thread ID
- Event Type – Informational, Warnings, Errors
- Source – Name of the log file, you should always know what log you're in.
- Description – What actually happened. Detailed errors, processing information, this is usually what you need to know.
Debug Logs Description
<GFI MailEssentials installation path>\GFI\MailEssentials\DebugLogs
|
Filename |
Description |
|
ASConfigurationServices.log |
Anti-Spam engine configuration log |
|
AutoUpdate.log |
Debug log file for the updating functionality log file |
|
E2k7wizard.log |
Debug log file for the Post Installation Wizard |
|
gfimdb.txt |
Debug log file for the module that is used to access avapicfg.mdb. This module is also used by CS, when it needs to read and write to the configuration file. |
|
IISVirtualDirectory.log |
IIS debug logs |
|
repository.gfi_log.txt |
Debug log file for the Repository module - the module which unloads and reloads the virus scanning modules and the EED (Email Exploit Detector) when new updates are available |
|
SID.log |
Debug log file for AD Queries for user accounts |
|
Switchboard.log |
Debug log file for Switchboard activity |
|
unpackplg.txt |
Debug log file for the modules which analyze compressed attachments |
|
unpckeng.txt |
Debug log file for the engine which manages the unpack plugins |
|
Usertimecnt.txt |
Debug log file for the module that counts the number of users and the number of days elapsed since the installation |
<GFI MailEssentials installation path>\GFI\MailEssentials\Antispam\DebugLogs
|
Filename |
Description |
|
ADBRobot.gfi_log.txt |
Debug log file for the ADBRobot module – the module that takes care of the remote commands sent in emails from the Administrator |
|
Antiphish2.txt |
Debug log file for the Antiphish2 module – the module that is loaded by the MES Legacy Attendant service, and used to check for new updates of the PURBL database. |
|
ase.gfi_log.txt |
Debug log file for the AntiSpam Engine (ASE). This engine loads all the Anti-Spam modules. |
|
Ase_action.gfi_log.txt |
This debug log file logs one line of log for each email that is processed by the ASE. This will allow us to easily identify the action that has been by the ASE on the email. Emails are identified by MessageIDs, however no MessageID is available for emails scanned at SMTP level. |
|
ase_antispoofing.gfi_log.txt |
Debug log for the Antispoofing module |
|
ase_bayesian.gfi_log.txt |
Debug log for the Bayesian module |
|
ase_blacklist.gfi_log.txt |
Debug log file for the Email Blacklist module |
|
ase_dirharvest.gfi_log.txt |
Debug log file for the Directory harvesting module (both AD and LDAP) |
|
ase_dnsbl.gfi_log.txt |
Debug log file for the DNSBL Anti-Spam module |
|
ase_greylisting.gfi_log.txt |
Debug log for the Greylisting module |
|
ase_greylisting_maint.gfi_log.txt |
Debug log for the Greylisting maintenance jobs (Deletion of triplets from the temporary and authorized table) |
|
ase_header_check.gfi_log.txt |
Debug log file for the module that takes care of the header checking |
|
ase_ipblocklist.gfi_log.txt |
Debug log file for the IP Blockslit module |
|
ase_ipwhitelist.gfi_log.txt |
Debug log file for the IP Whitelist module |
|
ase_keyword_checking.gfi_log.txt |
Debug log file for the module that takes care of the Keyword checking |
|
ase_kwhite.gfi_log.txt |
Debug log file for the Keyword Whitelist |
|
ase_language_detection.gfi_log.txt |
Debug log file for the Language Detection module |
|
ase_personalblocklist.gfi_log.txt |
Debug log file for the Personal Blocklist module |
|
ase_personalwhitelist.gfi_log.txt |
Debug log file for the Personal Whitelist module |
|
ase_purbl.gfi_log.txt |
Debug log file for the PURBL module |
|
ase_spamrazer.gfi_log.txt |
Debug log file for the module which manages the MailShell engine |
|
ase_spf.txt |
Debug log file for the SPF module |
|
ase_surbl.gfi_log.txt |
Debug log file for the SURBL Anti-Spam module |
|
ase_whitelist.gfi_log.txt |
Debug log file for the Whitelist module |
|
ase-scan_inbound.gfi_log.txt |
Shows the Antispam filters processing each email in Full Email mode according to the Filter Priority set |
|
ase-scan_smtpindata.gfi_log.txt |
Shows the Antispam filters processing each email in SMTP Transmission mode according to the Filter Priority set |
|
Aswiz.log |
The log file for the Bayesian Wizard |
|
Audldownload.txt |
Debug log file of the module that does the downloading of the Bayesian Spam database and the Antiphishing module updates from the GFI web site |
|
AuSpamRazer.gfi_log.txt |
Debug log file for the module that triggers the updating of the files used by the SpamRazer engine |
|
Autopatchchk.txt |
Debug log file for the autopatchchk module. This module is used to check for new patches available on our site. It does this by posting information regarding the build number of MES installation to an online ASP hosted at our site. The ASP will return information on any patches available. The process can also be started manually from the MES config. |
|
AutoReplies.gfi_log.txt |
Debug log file for the AutoReplies module |
|
Autospamsvc.txt |
Debug log file for the audldownload module that is started by the MES Legacy Attendant service. This module takes care of checking for new Bayesian Spam database on our site. Logging is also done to this log file when the checking for a new database is initiated manually from the MES config. |
|
Autoupui.gfi_log.txt |
Debug log file for the module which is loaded by the MES configuration when the PURBL database update is started from the configuration. |
|
AutoWhiteList.gfi_log.txt |
Debug log file for the AutoWhiteList module |
|
Awi.log |
Debug log file for the AWI (Archive Web Interface) module |
|
ChecklicXX.txt |
Debug log file for the module that is checking the MES license. Lists the Licensed users and the number of elapsed evaluation days. Useful for troubleshooting licensing problems. This module is the main module that provides information on the license. All the other modules that require information on the License will make use of functions from this module. |
|
ConfigurationServices.log |
Debug log file for the ConfigurationServices module, which is loaded by the MES Managed Attendant service, and currently used only by the Exchange 2007/2010/2013/2016 Transport Agents |
|
ContScan.log |
Debug log file for the Keyword Content Checking module |
|
DashBoard.log |
Debug log file for the DashBoard UI |
|
Digest.reporting.log |
Debug log file for the module used by the Email Spam Digest module to read data from the reports database and generate xml files, which are used by MEDigest to send the digest emails |
|
disclaimer.gfi_log.txt |
Debug log file for the Disclaimer module |
|
DNSCCore.gfi_log.txt |
Debug log file of the module that is used to perform the DNS tests |
|
DNSChecker.gfi_log.txt |
Debug log file for the module that periodically instructs the DNSCCore module to perform the DNS tests |
|
E2k7wizard.log |
The debug log file for the Exchange 2010/2013/2016/2019 wizard launched after the installation of MES, and during the un-install of MES |
|
EArchiveIn.gfi_log.txt |
Debug log files for the EArchiveIn module. This is the debug log file for the inbound Mail Monitoring module. |
|
EArchiveOut.gfi_log.txt |
Debug log files for the EArchiveOut module. This is the debug log file for the outbound Mail Monitoring module. |
|
EmailPrefetch.gfi_log.txt |
COM object used by the MTA. When scanning an email, EmailPrefetch is used to retrieve information from the Received lines (so that this is only done once, rather than have each module do it individually) |
|
Exploder@*.gfi_log.txt |
Debug log file written by the List Server Queue module. This log file will contain logging of the transactions done with the Exploder queues. The number after the @ sign may increase indicating that multiple queues have been created to keep up with the email flow. |
|
Footer@*.gfi_log.txt |
Debug log file written by the List Server Queue module. This log file will contain logging of the transactions done with the Footer queues. The number after the @ sign may increase indicating that multiple queues have been created to keep up with the email flow. |
|
GFI.Common.Tracing.log |
This debug log file is used whenever the module requesting to write the log does not specify the name of the log file to be used |
|
GfiAsRtRoutedAgent.log |
Debug log file of the GfiAsRtRoutedAgent Exchange 2007/2010/2013/2016 Transport Agent, which provides outbound emails to be processed just before they are sent |
|
GfiAsRtSubmittedAgent.log |
Debug log file of the GfiAsRtSubmittedAgent Exchange 2010/2013/2016/2019 Transport Agent which provides inbound emails to be processed as soon as they are fully received |
|
GfiAvRoutingAgent.log |
Debug log file of the GfiAvRoutingAgent Exchange 2010/2013/2016/2019 Transport Agent |
|
GfiMeSmtpAgent.log |
Debug log file of the GfiMeSmtpAgent Exchange 2010/2013/2016/2019 Transport Agent |
|
gfiBDB.gfi_log.txt |
Debug log file for the module used to read/write/update the PURBL database – blocklist.db. All modules which need to access this database need to make use of gfiBDB. |
|
Gfiavuser.log |
Module that retrieves Exchange information when MailEssentials is installed on the same machine as Exchange server. This information is used to connect to the Exchange server when counting mailboxes. |
|
Gfiscans.gfi_log.txt |
Debug log file for the GFI MailEssentials Scan Engine service (referred to as GFISCANS in this document) |
|
InSink.gfi_log.txt |
Debug log file for the Inbound Sink. |
|
libSpam.gfi_log.txt |
Debug log file for the module that provides an interface to the Bayesian database and the Bayesian tok files. All the modules that make use of these files will have to do that through this library. |
|
libSpamAtt.gfi_log.txt |
Debug log file for the Bayesian module which is used to read and write information related to attachments in the Bayesian database |
|
licsvc.txt |
Debug log file for the module that is checking the license and will send notifications when necessary (e.g. 15 days before the Evaluation expires) |
|
Listserv.gfi_log.txt |
Debug log file for the List server Service |
|
Ls_footer.gfi_log.txt |
Debug log file of the Footer module which is part of the List server. |
|
Ls_mta.gfi_log.txt |
Debug log file of the List server MTA |
|
Ls_mta_poller.gfi_log.txt |
Debug log file for the List server MTA checking the license key |
|
Ls_pickup.gfi_log.txt |
Debug log file of the List Server Pickup module |
|
LSPreproceessor.gfi_log.txt |
Debug log file of the List Server Preprocessor module |
|
lsQ.gfi_log.txt |
Debug log file of the List Server Queue module |
|
LSScrubber.gfi_log.txt |
Debug log file of the List Server Scrubber module |
|
LSSubscriber.gfi_log.txt |
Debug log file of the List Server Subscriber module |
|
LSXploder.gfi_log.txt |
Debug log file of the Exploder module which is part of the List server |
|
Ltvsatt.txt |
Debug log file of the MES Legacy Attendant |
|
Ltvsmon.txt |
Debug log file for the GFI Monitor interface. This will log retrieval of GUI and other settings when loading and unloading the Monitor. |
|
MailEssentials.ControlLists.AWL.log |
Debug log file for Autowhitelist |
|
MailEssentials.ControlLists.DAL.log |
Debug log for Data Access Layer which writes data to the ControlLists.sdf database |
|
MailEssentials.ControlLists.GBL.log |
Debug log file for Global Blocklist |
|
MailEssentials.ControlLists.GWL.log |
Debug log file for Global Whitelist |
|
MailEssentials.ControlLists.PBL.log |
Debug log file for Personal Blocklist |
|
MailEssentials.ControlLists.PWL.log |
Debug log file for Personal Whitelist |
|
MailReaper.gfi_log.txt |
Debug log for the MailReaper module – the module that will update ham_tmp.tok with information from outbound emails (considered to be good – ham – emails) |
|
MailRoute_mta.gfi_log.txt |
Debug log file for the MailRoute module. This log file will contain logging of emails that are submitted to the mailroute module from the MailEssentials MTA |
|
MailRoute_sink.gfi_log.txt |
Debug log file for the MailRoute module. This log file will contain logging of emails that are submitted to the mailroute module directly from the IIS Sink (in the case of internal emails from Exchange server) |
|
Mailroutewrapper.gfi_log.txt |
Debug log file for the MailRouteWrapper module. This module is only used when MES is installed on the same machine as Exchange 2010/2013/2016/2019. |
|
Mebackup.gfi_log.txt |
Debug log file for the MailEssentials Configuration Backup utility (meconfigmgr.exe) |
|
MEC.QAS.Tagging.log |
Debug log file used when the ASE action is Tagging and Append block reason |
|
MEDashBoardPlugin.log |
Debug log file for the Managed Attendant Remoting plug-in which is used to provide all the information and data required by the Dashboard |
|
MEDigest.log |
Debug log file for the module which is loaded by the Managed Attendant and which is triggered to send email digests to the administrator and users |
|
MEReports.log |
Debug log file for the Reporter User Interface |
|
mescfg.txt |
Debug log file for the MailEssentials configuration |
|
Middleman_gfiscan.gfi_log.txt |
Debug log file for the module that writes information on blocked email to the MEC MSMQ queues. This module receives information from the MES scanning engine. |
|
Middleman_midlayer.gfi_log.txt |
Debug log file for the module that reads information on blocked emails from the MES MSMQ queues. This module is instructed to read this information from the MES Legacy Attendant > QASC. |
|
Middleman_midlayer_recovery.gfi_log.txt |
When a failure occurs in one of the QASC plug-ins, the information on the email is saved to the queue, and this information is read again when the MES Legacy attendant is restarted. This log file will log this process. |
|
Msghlps.gfi_log.txt |
Log file for the module that ‘helps’ CDO not corrupt the messages build by MailEssentials. Basically, this module will hide parts of the email header that will cause CDO to corrupt the email. |
|
MTA.gfi_log.txt |
Debug log file for the MailEssentials Message Transfer Agent (MTA). The MTA is a key component of MailEssentials. It controls all the plug-ins and engines. The MTA is the bridge between the Inbound/Outbound sinks or the SMTP/Transport agents and the plug-ins. |
|
MTA_Poller.gfi_log.txt |
Debug log for a thread in the MTA that is checking if the Refresh registry key has changed once every 10 seconds. When there is a change in the configuration, the Refresh registry value is changed. This module will detect the change and instructs the MTA to reload the configuration for all the modules. |
|
mtaprox.txt |
Log file for the module that takes care of changing the refresh registry key when there is a change in the confirmation or when the modules are required to reload the configuration |
|
Mvexch_stub.gfi_log.txt |
Debug log file for the MvexchStub. This module is used only when MES is installed on the same machine as Exchange 2010/2013/2016/2019, and is used to provide ’Move to sub-folder of user’s mailbox’ functionality. |
|
Mvexch.gfi_log.txt |
Log file of the module that moves spam emails to the users mailboxes when MES is installed on the same machine as Exchange server 2003 |
|
Newsenders.gfi_log.txt |
Debug log file for the NewSenders module |
|
NotificationServices.log |
Debug log file for sending out email notifications |
|
OutSink.gfi_log.txt |
Debug log file for the Outbound Sink |
|
Patchsvc.txt |
Debug log file of the module that is started by the MES Legacy Attendant service. This module takes care of checking for new patches (using autopatchchk module). Logging is also done to this log file when the checking is initiated manually from the MES config. This module will also take care of creating a notification email and saving it to the IIS pickup directory when a new patch is available. |
|
PFolders.gfi_log.txt |
Debug log file for the PFolders module - Anti-Spam folders (Public folders) accessed using MAPI protocol. Module not used - obsolete. |
|
PFTrain.log |
Debug log file for the WebDav Public Folder Scanning module. This module is hosted by the GFI MailEssentials Managed Attendant module. |
|
PickupSM.log |
Debug log file for the Pickup Submission Module |
|
Pop2exchange_*.log |
Log files for the different mailboxes configured in the P2E configuration. These log files are only created when the debug registry key is enabled (=1) and the debug value in the [Pop2Exchange] sub registry key is equal to ‘8’ (procedure in erl). |
|
PopConfig.log |
Debug log for the loading, reading and updating of the P2E configuration |
|
PopService.log |
Debug log file for the POP2Exchange service and the checking for new emails by the P2E |
|
PreProcessor@*.gfi_log.txt |
Debug log file written by the List Server Queue module. This log file will contain logging of the transactions done with the Preprocessor queues. The number after the @ sign may increase indicating that multiple queues have been created to keep up with the email flow. |
|
PWLBL-DBHandling.log |
Debug log for the Personal Whitelist and Blacklist Handler module |
|
QAS.ForwardMail.log |
Debug log file for the Quarantine Actions Services |
|
QAS.MTEF.log |
Debug log file used when the ASE action is to move to exchange folder |
|
QAS.SaveToDisk.log |
Debug log file used when the ASE action is to save a copy of spam |
|
QAS.SendFakeNDR.log |
Debug log file used when the ASE action is to send a fake NDR |
|
QAS.WriteCSV.log |
Debug log file used when the ASE action is to log the occurrence to a file |
|
QASCoordinator.log |
Debug log file for the Quarantine Actions Services Coordinator – the module which loads the QASC plug-ins. This module is loaded by the MES Managed attendant service. |
|
Quar.log |
Log file for the Quarantine action database access and maintenance |
|
QuarDigest.log |
Debug log for the Quarantine digest |
|
QuarQA.log |
Debug log for the QASC ASE action to save email in the Quarantine database. |
|
Qstats.gfi_log.txt |
Debug log file written by the List Server Queue showing statistic information for the list server when it is accessing the Queues |
|
Received.gfi_log.txt |
Debug log file for the module that is responsible for logging inbound emails in the Reporting database |
|
Regcount44.gfi_log.txt |
Debug log file that will log information from the MES Legacy Attendant Service (licensing information). This file is normally not useful for support. |
|
RemotingPlugin.log |
Debug Log file for the RemotingPlugin – this is hosted by the MES Managed Attendant service, and is used to expose the functionality of modules used by the same service to other processes |
|
Repdbcon.log |
Debug log file for the tools that is used to import the ME9 Reporter’s database (data.mdb) to the ME10+ database |
|
Reports.gfi_log.txt |
Debug log file used of the reporting interface (reports.dll), which is used by reporting, dashboard and spam digest functionality |
|
Reports.log |
Debug log file for the Reporting engine. This is the module that actually checks the filtering options and has the logic for generating reports |
|
RPFolders.gfi_log.txt |
Debug log file for the RPFolders module - Anti-Spam folders (Public Folders) accessed using IMAP protocol |
|
Rule.gfi_log.txt |
Debug log file of the module used by the Rules manager to access Exchange server and create server side rules |
|
RulesManager.gfi_log.txt |
Debug log file for the Rules manager |
|
Scrubber@*.gfi_log.txt |
Debug log file written by the List Server Queue module. This log file will contain logging of the transactions done with the Scrubber queues. The number after the @ sign may increase indicating that multiple queues have been created to keep up with the email flow. |
|
SendLog.gfi_log.txt |
Debug log file for the module that is responsible for logging outbound emails in the Reporting database |
|
Smtpaddressbook.txt |
Log file for the GUI that shows the users when MES is retrieving users from the internal users database (userlist.mdb) |
|
SmtpInSink.gfi_log.txt |
DebugLog file for the SmtpInSink IIS SMTP Event sink, which is used to scan emails at SMTP level |
|
Software_gfi_mex_engines_inbound.log |
Log file that shows error logging when there is a failure in a module that is loaded by the InboundSink |
|
software_gfi_mex_engines_listserv.log |
Log file that shows error logging when there is a failure in a module that is loaded by the ListServ |
|
software_gfi_mex_engines_outbound.log |
Log file that shows error logging when there is a failure in a module that is loaded by the Outbound Sink |
|
software_gfi_mex_engines_inbound_ase.log |
Log file that shows error logging when there is a failure in a module that is loaded by the ASE engine |
|
Spamord.log |
Debug log file for the module that changes the order of the ASE plug-ins |
|
Stats.reporting.log |
Debuglog file of the module that is used to retrieve data from the Reports database. This data is used to display the statistics in the Evaluation page displayed when the client loads the ME config during the evaluation. |
|
Subscribe@*.gfi_log.txt |
Debug log file written by the List Server Queue module. This log file will contain logging of the transactions done with the Subscribe queues. The number after the @ sign may increase indicating that multiple queues have been created to keep up with the email flow. |
|
TicketManager.log |
Debuglog file for the TicketManager. This module is used only when MES is installed on the same machine as Exchange 2007/2010/2013/2016. |
|
TNEF2MIME.gfi_log.txt |
Debuglog file for the TNEF2MIME module – this module is used by the MailRoute when it needs to process TNEF emails originating directly from Exchange server (normally internal emails in Exchange server) |
|
Unpackplg.txt |
Module that takes care of retrieving information from TNEF emails. This information is used to build the MIME messages. |
|
usercntado.txt |
Debug log for the module that counts users when the MailEssentials is installed in SMTP mode |
|
Usercntad.log |
Debug log for the module that counts users when the MailEssentials is installed in AD mode. Will list all the users that are counted from AD. |
|
Usercntvsapi.txt |
Log file for the module that counts users when MES is installed on the same machine as Exchange server. Exchange mailboxes are counted in this case. |
|
usertimecnt.txt |
Debug log file for the module that counts the amount of users and the number of days elapsed since the installation |
|
Usercntdmn.gfi_log.txt |
Debug log file for the UserCntDmn module. This module counts the list of mailbox users having an e-mail address on the local e-mail domain being scanned. This applies to Exchange user counting only. |
|
Usercollect.txt |
Debug log file for the module that collects email addresses from outbound emails and dumps them to the user configuration. This is done only when userlist.mdb is used. |
|
usrlkado.txt |
Debug log file for user lookups for MailEssentials in SMTP mode (user lookups are performed on the userlist.mdb created by MailEssentials installation) |
<GFI MailEssentials installation path>\GFI\MailEssentials\Backend\DebugLogs
|
Filename |
Description |
|
AttendantService.log |
Debug log file for the Attendant service – this will show the loading and unloading of the various modules loaded by this service |
|
Centralization.log |
Debug log file for the Multi-Server module |
|
CentralizedQuarantine.log |
Debug log file for the Multi-Server module for the machine hosting the Quarantine database |
|
CentralizedReporting.log |
Debug log file for the Multi-Server module for the machine hosting the Reporting database |
|
QSS.log |
Debug log file for the Quarantine Store Services (QSS) plug-in – the plug-in which provides an interface to the Quarantine Store. This module is loaded by the Attendant > Remoting Host. |
|
QSSItemsDalFb.log |
Debug log for items parts quarantined |
|
QSSMSecFbDalPlugin.log |
Shows loading and unloading of DALPlugin |
|
QSSMSecPlugin.log |
Shows loading and unloading of MSec Plugin |
|
QSSRawDataDalFBF.log |
Shows initialization and un-initialization of QSSRawDataDalFBF module |
|
Quar.log |
Debug log file for Quarantine activity |
|
QuarDigest.log |
Debug log file for creating and sending out the Quarantine Digest to the users |
|
RemotingPlugin.log |
Debug log file for the Remoting module – the module that loads a set of plug-ins, which are used to provide a specific service to other modules. This module is loaded by the Attendant service. |
|
ReportingActivity.log |
Debug log file for the writing of data from MSMQ Report Queues to the Reports database |
|
ReportingGenerator.log |
Debug log file for when generating a report |
|
ReportingHelper.log |
Debug log file for the module that provides information from <GFI\ContentSecurity\MailSecurity\GFIMon> to the Realtime Monitor in the Web interface. This module is loaded by the Attendant > Remoting Host. |
|
RSSPlugins.log |
Debug log file for the RSS Plugin. This plugin is used to write the RSS XML files, and to read from them when the web application requires this RSS feeds. |
|
SpamDigest.log |
Debug log file for creating and sending out the Spam Digest to the Administrator or the specified user. |
<GFI MailEssentials installation path>\GFI\MailEssentials\Attendant\DebugLogs
|
Filename |
Description |
|
AutoUpdate.log |
Debug log file for the AutoUpdate service |
|
Centralization.log |
Debug log file for the Multi-Server module |
|
CentralizationConfiguration.log |
Debug log file for the configuration of the Multi-Server module |
|
CentralizedConfiguration.TransferMonitor.log |
Debug log file for the synchronization activity between servers connected through the Multi-Server module |
|
Checklic.log |
Debug log for the License checker module that evaluates data provided by the key decoder and the user counting module and compares them against each other. |
|
ChecklicXX.txt |
Debug log file for the module that is checking the MES license. Lists the Licensed users and the number of elapsed evaluation days. Useful for troubleshooting licensing problems. This module is the main module that provides information on the license. All the other modules that require information on the License will make use of functions from this module. |
|
ConfigurationServices.log |
Debug log file for the ConfigurationServices module, which is loaded by the MES Managed Attendant service, and currently used only by the Exchange 2010/2013/2016/2019 Transport Agents |
|
libSpam.gfi_log.txt |
Debug log file for the module that provides an interface to the Bayesian database and the Bayesian tok files. All the modules that make use of these files will have to do that through this library. |
|
libSpamAtt.gfi_log.txt |
Debug log file for the Bayesian module which is used to read and write information related to attachments in the Bayesian database |
|
MailEssentials.ControlLists.AWL.log |
Debug log file for Autowhitelist |
|
MailEssentials.ControlLists.DAL.log |
Debug log for Data Access Layer which writes data to the ControlLists.sdf database |
|
MailEssentials.ControlLists.GBL.log |
Debug log file for Global Blocklist |
|
MailEssentials.ControlLists.GWL.log |
Debug log file for Global Whitelist |
|
MailEssentials.ControlLists.PBL.log |
Debug log file for Personal Blocklist |
|
MailEssentials.ControlLists.PWL.log |
Debug log file for Personal Whitelist |
|
NotificationServices.log |
Debug log file for sending out email notifications |
|
PFTrain.log |
Debug log file for the WebDav Public Folder Scanning module. This module is hosted by the GFI MailEssentials Managed Attendant module. |
|
PFTrainEWS.log |
Debug log file for the EWS Public Folder Scanning module. This module is hosted by the GFI MailEssentials Managed Attendant module. |
|
PickupSM.gfi_log.txt |
Debug log file for the Pickup Submission Module |
|
RCRemote.log |
Debug log file for the Remote Commands module |
|
RemotingPlugin.log |
Debug Log file for the RemotingPlugin – this is hosted by the Attendant service, and is used to expose the functionality of modules used by the same service to other processes |
|
TicketManagerCore.log |
Debug log file for the TicketManager. This module is used only when MES is installed on the same machine as Exchange 2010/2013/2016/2019. |
<GFI MailEssentials installation path>\GFI\MailEssentials\WwwConf\DebugLogs
|
Filename |
Description |
|
ConfigurationUI.log |
Debug log file for the web application in general. This will normally log errors that effect the Web Application as a whole. |
|
FE10Configuration.log |
Front End configuration Debug log file. This is the log file for the module that is used to read from the Web Application configuration. |
|
FE10Host.log |
Debug log file for the module which parses ASPX pages which need to be provided to the user |
|
FrontPage.log |
Debug log file for the root page – the one shown when you click on Console Root |
|
Navigation.log |
Debug log file for the ASPX page which provides the Navigation pane in the UI |
|
Newfilter.log |
DebugLog file for the UI of when the user selects to create or edit a user-defined filter |
|
QFE_CacheHelper.log |
Debug log file for one of the QFE module used by QFE_QuarantineList, which provides Caching for the requests done by the user. Only Quarantine lists are cached. |
|
QFE_ItemDetails.log |
Debug log file for the QFE module that is used to provide details on specific Quarantine items. The features provided in the quarantine item details like download email and rescanning of an email are also logged to this file. |
|
QFE_Monitor.log |
Debug log file for the Real-time monitor displayed in the MSEC Web UI |
|
QFE_Quarantinelist.log |
Debug log file of the QFE module that loads the list of quarantine items. This can be done from one of the default filters, from the user-defined search folders, or from the quick search function. |
|
QFE_Root.log |
Debug log file for the QFE module which provides the UI for the Quarantine Root and the Search Folders Root – this is basically the same interface |
|
Qsssearchfolders.log |
Debug log file for the ‘Quarantine RSS Feeds’ interface in the main MailEssentials UI |
|
RewriterModule.log |
Debug log file for the ReWriter module – the debug log file that will map the users’ requests to an aspx page on disk |
|
Vsnodes.log |
Debug log file for the interface of the Virus scanning engines nodes |
|
WebLocalization.log |
Debug log file for the module that will be used to provide MailEssentials UI in different languages. Currently, only English is used. |
Priyanka Bhotika
Comments