Audit Log - Revision history

Ltalaschus at 12:29, 25 September 2025

2025-09-25T12:29:44Z

2025-09-25T10:05:41Z

2025-09-25T10:00:16Z

2025-09-25T09:51:16Z

2025-09-25T09:49:57Z

2025-09-25T09:42:35Z

2025-09-25T08:35:43Z

2025-09-23T15:21:38Z

2025-09-23T15:15:42Z

Exporting the Audit Log

2025-09-23T15:00:39Z

@@ Line 18: / Line 18: @@
 * Only audit log events from the integrated log can be exported.
 * One CSV file is created per day.
-* If the delete option is enabled data for a day will be deleted from the internal log only after it has been exported also.
+* If the delete option is enabled, data for a day will be deleted from the internal log only after it has been exported also.
 * Only entire days can be exported.
 * The current day cannot be exported.
-* The timestamp of the files are in UTC.
+* The timestamps of the files are in UTC.
-* The timestamp of the events in the files are in UTC.
+* The timestamps of the events in the files are in UTC.
 * The process can be canceled. If the delete option is enabled, events that have already been deleted will not be restored.
 * Only events older than 30 days can be deleted.

@@ Line 14: / Line 14: @@
 == Exporting the Audit Log ==
-The audit log can be exported in CSV format. This can be useful when audit entries shall be analyzed with an external tool or when old entries should be purged.
+The audit log can be exported in CSV format. This can be useful when audit events shall be analyzed with an external tool or when old events should be purged.
-* Only audit log entries from the integrated log can be exported.
+* Only audit log events from the integrated log can be exported.
 * One CSV file is created per day.
 * If the delete option is enabled data for a day will be deleted from the internal log only after it has been exported also.
 * Only entire days can be exported.
 * The current day cannot be exported.
-* The timestamp of the files is in UTC.
+* The timestamp of the files are in UTC.
-* The timestamp of the entries in the files is in UTC.
+* The timestamp of the events in the files are in UTC.
-* The process can be canceled. If the delete option is enabled, entries that have already been deleted will not be restored.
+* The process can be canceled. If the delete option is enabled, events that have already been deleted will not be restored.
 * Only events older than 30 days can be deleted.
 * If the target directory already contains files, they may be overwritten.

@@ Line 18: / Line 18: @@
 * Only audit log entries from the integrated log can be exported.
 * One CSV file is created per day.
-* If the delete option is enabled audit data will be deleted from the internal log only after it has been exported also.
+* If the delete option is enabled data for a day will be deleted from the internal log only after it has been exported also.
 * Only entire days can be exported.
 * The current day cannot be exported.

@@ Line 34: / Line 34: @@
 * Click the ''Export'' button below the table.
 *:[[File:Compliance_auditlog_02.png|center]]
-* Select the date up to which you want to export the data. By default, the date 90 days in the past is selected.
+* Select the date up to which you want to export the data. By default a date of 90 days in the past is selected.
 * Select a target directory for the exported files.
 * Select whether the exported data should be deleted from MailStore. The date will be automatically adjusted if it is less than 30 days in the past.

@@ Line 18: / Line 18: @@
 * Only audit log entries from the integrated log can be exported.
 * One CSV file is created per day.
-* If the delete option is enabled, after a day is exported, that day will be deleted from the internal log.
+* If the delete option is enabled audit data will be deleted from the internal log only after it has been exported also.
 * Only entire days can be exported.
 * The current day cannot be exported.

@@ Line 1: / Line 1: @@
 If MailStore's own audit log is used for logging audit events (default), this audit log can be retrieved via MailStore Client.
-'''Please note:''' If the Windows Eventlog is used as destination for logging of audit events, the ''Audit Log'' option at ''Administrative Tools'' > ''Compliance'' is not shown. In that case, use the your favorite method for retrieving information from the Windows Eventlog.
+'''Please note:''' If the Windows Eventlog is used as destination for logging of audit events, the ''Audit Log'' option at ''Administrative Tools'' > ''Compliance'' is not shown. In that case, use your favorite method for retrieving information from the Windows Eventlog.
 == Retrieving the Audit Log ==

@@ Line 28: / Line 28: @@
 * To load the CSV files into Excel, use the data import function available there.
-To export, proceed as follows:
+'''To export, proceed as follows:'''
 * Start the MailStore Client and log in as the MailStore administrator.

@@ Line 8: / Line 8: @@
 * Start MailStore Client and log on as a MailStore administrator (''admin'').
 * Click ''Administrative Tools'' > ''Compliance'' and then ''Audit Log''.
 * The events to be fetched from the audit log can be filtered by modifying the settings for ''Date Range'', ''User Name'', ''User Activity Type'' and ''Maximum Number of Results''.
 * Click on ''Retrieve''.
 * The matching events are shown in the table. To show further details of an event, double-click on the corresponding table row.
 [[de:Audit-Protokoll]]
 [[en:Audit Log]]