What do the events recorded in the Application Event Log mean for Mail Utilities?

Symptoms

I'm getting event log entries recorded in the application event log, and I don't know what they mean.

Cause

Exclaimer will write various entries to the application event log when certain events occur. This knowledge base article describes the events and under what circumstances they would be written to the event log.

More Information

Event Log ID	Severity	Description	More information
1	Error	There was an unhandled exception whilst processing an SMTP message in the command %1. The message will not be affected.	An error was trapped during Exclaimer execution that was not forseen during development, but to prevent this error from terminating the INETINFO process, Exclaimer trapped this and reported it to the event log. If this event occurs occasionally you can safely ignore this event, but if it occurs on a regular basis, it may point to an infrastructure problem.
2	Error	eXclaimer was unable to open the file %1. The error was %2. Logging was disabled.	This error is generated if Exclaimer cannot open it's log file for output. This may be generated if some other process has the file open already, such as Word. It may also be caused by a folder permissions problem. Under these circumstances, Exclaimer logging was disabled.
3	Error	eXclaimer was unable to open the file %1 in thread %2. The file was locked for an unacceptable period of time.	This error can occur if the log file is locked for an unacceptable period of time (>10 minutes) and an Exclaimer process wishes to write to it to add more logging information. If the INETINFO process is terminated at this time, then logging information may be lost.
4	Info	An Exclaimer message sink was loaded	A sink is the unit of code that processes messages on behalf of Exchange or the Windows 2000/2003 SMTP event service. The Exclaimer sink was loaded to perform this work
5	Info	An Exclaimer message sink was unloaded	A previously loaded sink was unloaded.
6	Info	The process %1 loaded the Exclaimer DLL %2	A process has loaded the Exclaimer DLL. Under normal execution, this process will be INETINFO.EXE, but other processes may load it. These are notably MSHTA.EXE - The user interface control panel REGSVR32.EXE - The windows registration tool PERFMON.EXE - The windows performance monitor REGSVC.EXE - The remote permformance monitor
7	Info	The process %1 unloaded the Exclaimer DLL %2	One of the previous processes to load the Exclaimer DLL has unloaded it.
8	Info	The process %1 registered the Exclaimer DLL %2	The Exclaimer DLL was registered by the calling processes.
9	Info	The process %1 unregistered the Exclaimer DLL %2	The Exclaimer DLL was unregistered by the calling process.
16	Error	Message %1 from %2 had failure code %3. Last error line was %4. This message will continue to be delivered	The following group of errors relate to what has happened to a message when any error occurs in the system. The action that Exclaimer takes is based on the fault tolerance settings in the Advanced dialog box
17	Error	Message %1 from %2 had failure code %3. Last error line was %4. This message will be aborted
18	Error	Message %1 from %2 had failure code %3. Last error line was %4. This message will be quarantined
19	Error	Message %1 from %2 had failure code %3. Last error line was %4. The SMTP service will be stopped
20	Error	Message %1 from %2 had failure code %3. Last error line was %4. This message should have been quarantined, but that failed, so it will continue delivery
21	Error	Invalid Exclaimer License: %1	You have an invalid Exclaimer license. The error report will be more details.
22	Error	"C" Runtime stub "%1" called. Error log will contain more details.	The Exclaimer error log will contain further details of this error.
23	Error	Unhandled exception %1 trapped in Exclaimer. MiniDump file is %2	The mini-dump file contains the state of the system at the point of this error. Please send this file with a description of your infrastructure to support@exclaimer.com
24	Error	Exception %1 occured	An error occured whilst handling another error.