MTA / mail server logs do not appear in Status > Logs
search cancel

MTA / mail server logs do not appear in Status > Logs

book

Article ID: 408441

calendar_today

Updated On:

Products

Messaging Gateway

Issue/Introduction

No matter what log level is set, no MTA logs appear in the Status > Logs log view. Log data from other SMG services appear in the Status > Logs page but no logs from the MTA service are available.

Environment

Version: 10.8.0, 10.8.1, 10.9.0, 10.9.1

Cause

This is a defect where the format of the log timestamp is causing a failure to transfer the MTA logs to the database due to the timezone format in the log entries. MTA logs with a negative GMT offset for the timezone are not inserted into the database

2025 Aug  8 14:01:02 -03 (info) ecelerity: [71410] ML-HOST_CONNECTED: 10.0.0.1:54321 connected. (ID: 7f51a364fb00) 

Resolution

This issue will be addressed in a future Messaging Gateway release.

Workaround

This issue may be worked around by selecting a timezone with an alphanumeric representation like PDT or 

  1. Log into the Control Center web application as an administrator
  2. For each scanner go to Administration > Configuration > [scanner] > DNS / Time
  3. Select an alternate timezone with the same GMT offset as your configured timezone (North American timezones appear to be less affected than South American timezones)
  4. Click Save

The Control Center will begin inserting new logs into the database following the change. Older log entries cannot be collected through this method since their timezone format is what triggers the defect.

Example:

Switching from Brasilia as the timezone to Greenland which has the same GMT offset will address the issue since Greenland's timezone is logged as "ADT" rather than "-03":