6 - Logging

This chapter ties together references to all the logging-related config settings documented elsewhere.


6.1 - Trace Logs

This is the most general type of logging, and provides general info, progress and error messages of varying (and configurable) verbosity from within the mailserver.
Logger messages are tagged with their severity level (Error, Warning, Info, Trace, etc) and if you were looking for indications of a problem, this is where you would start.
Mailismus logging is performed by the GreyLog framework, which is described here.

The following trace logs are generated by Mailismus:

You should examine the Dispatcher logfiles on startup whenever you modify the config, as they display the final settings and can confirm that the config was parsed as expected.


6.2 - Transcripts

Whereas the logfiles provide an internal program-oriented view of what's going on, the transcripts record the SMTP protocol dialogue, and so they provide an external functional view.
They can therefore be evaluated by somebody without any knowledge of how Mailismus works.

The following instances of this logfile are generated by Mailismus:

The initial Mailismus settings will put these transcripts in the directory %DIRLOG%/transcripts.
You would normally only generate transcripts when you're troubleshooting suspected protocol issues, or want to get a snapshot of the some typical SMTP traffic after making a config change.


6.3 - Audit Logs

These provide a formal record of all messages handled by Mailismus, and contain one line per message summarising its final outcome.
Unlike the ephemeral troubleshooting-oriented nature of the trace logs and transcripts, they are intended to be suitable for permanent archival.

The following instances of this logfile are generated by Mailismus:

The initial Mailismus settings will put these logs under %DIRLOG%/audit.


6.4 - Windows Service

This refers to the Windows Service defined in §5. The Windows Service has its own logfile, which produces trace-level output in the same vein as the trace logs in §6.1, but as a non-Java component, it obviously has nothing to do with NAF.
The default NAF-Launcher config files place this in the same root directory as the NAF-Bootup logfile, and call it winservice.log.
See §5 for details.