Skip to Content
Browse documentation

MailTrack Logs and History

Find MailTrack collector diagnostics, Exim source logs and tracking history, with the exact mailtack.log filename and rotation behavior.

MailTrack reads Exim's native delivery log and stores indexed tracking history. Its own application log diagnoses collection and processing; it is separate from the mail delivery log.

Default locations

LocationPurpose
/var/log/eenos/mailtack.logMailTrack application/collector diagnostics. The current filename is mailtack.log, including this spelling.
/var/lib/eenos/mailtrack.dbSQLite tracking history and collector state; not a text log.
Exim's configured native mainlogSource delivery events consumed by MailTrack. A common path is /var/log/exim_mainlog; configuration can select another location.

The service unit is eenos-mailtrack.service. To inspect a recent bounded interval:

tail -n 100 /var/log/eenos/mailtack.log
journalctl -u eenos-mailtrack.service --since '1 hour ago' --no-pager -n 100

The journal helps with startup and service errors that may occur before the application log is available. It is not a duplicate delivery-history database.

Find the source delivery log

MailTrack discovers Exim's log_file_path, spool_directory, hostname and timezone. For an administrator configuration check:

/usr/sbin/exim -bP log_file_path spool_directory primary_hostname timezone

The collector resolves supported native paths and replaces Exim's %s component with main. A syslog-only setup does not provide the required native mainlog; datestamped or unresolved dynamic paths are rejected. Do not assume the conventional mainlog path applies to every server.

Investigate missing history

First compare the message's Exim ID and timestamp with the source mainlog. Then inspect collector diagnostics and the health information in Delivery Tracking. A message absent from the collector's available source cannot be reconstructed merely by refreshing the panel.

Check whether tracking was disabled, whether the relevant time range is retained, and whether collection has encountered read or database errors. /etc/mailtrack_disabled is the disable marker; do not remove it as a diagnostic shortcut. Use supported controls when changing tracking state.

Rotation and retention

The application logger rotates at 2 MiB, retaining up to five numbered backups. Packaged installations can additionally apply /etc/logrotate.d/eenos-mailtrack; the reviewed package uses daily rotation, compression, seven retained rotations and copytruncate. These are two separate mechanisms, so archive names and available history can differ.

Tracking database retention defaults to 30 days in the collector configuration. This does not set the retention of the application log or Exim mainlog. Clearing tracking history does not erase Exim's source logs, and removing a source log does not clear existing indexed history.

Do not reset the database to fix collection

Deleting the database or its SQLite sidecar files can lose history and collector state. Preserve evidence and use the documented tracking controls rather than deleting files or manually editing the database.