The CommuniGate Pro Server maintains supplementary Logs in addition to the main Server Log described above.
Supplementary Logs are designed to store the most important events of a certain type only.
Supplementary Log records are stored as text file lines: one record is stored on one line. Each record/line starts with a timestamp prefix: hh:mm:ss.ddd where hh is the hour, mm is the minute, ss is the second, and ddd is the millisecond of the moment when the record was generated.
New supplementary Log Files are created daily.
Use the WebAdmin Interface to examine supplementary Logs. Open the Logs section in the Monitor realm. Click to select the supplementary Logs type. A page opens, it lists the stored supplementary Log files. The current Log is marked with the asterisk symbol.
You should have the Can Monitor Server Access Right to view the supplementary Logs.
The supplementary Log files are created inside subdirectories of the SystemLogs subdirectory.
These Log files contain a record for each Server module or component setting update.
The following record format is used:
component userName newSettings
the updated component name
the name of the Administrator Account used to update the Settings.
the updated settings object value (usually - a dictionary).
These Log files contain Call Detail Records in various formats. See the Real-Time Signals section for more details.
The E-mail Transfer Dequeuer component generates a record for every E-mail delivery event. The following record format is used (the tabulation symbol is used as the field separator):
01 state returnPath fromAddress authAddress submitAddress localIP queueID messageID messageSize origRecipient module(queueName)recipient report
record format version
the message delivery result: RELAY (relayed), FINAL (delivered to the final destination), ERROR (a fatal error, resending will not help), TMPER (a temporary error condition, can be resent later).
message envelope return-path
the message From address
if the message sender was authenticated, the authenticated Account name. Otherwise, an empty string
the name of the component submitted the message, followed by the Network Address associated with the message source.
the Server Local Network Address used to submit the message
the message internal Queue UID (numeric)
the message Message-Id header field value