You can tell VPOP3 to send you a daily summary report each day.

To do this check the box to say Send daily summary logs to, and choose the appropriate user (or “Main Administrator” if you want the reports to be sent to the Main Administrator, whoever that is set as.

If you select Show Idle Accounts in the Summary log, then the report will contain a section showing accounts which have not been accessed within the last day

If you select Generate HTML format summary messages, then the report is generated in an HTML form, rather than plain text. Currently the message content is identical, whichever form you use. The HTML format messages can be useful if your email client displays plain text messages using a proportional font, as that causes the table alignments to be incorrect

The Keep raw summary log files in the SUMMARIES directory tells VPOP3 to keep the raw summary log files in the VPOP3\SUMMARIES directory instead of deleting them after generating the daily report. These are not used by VPOP3, but may be used by your own analysis tools.

The Keep MAIL.LOG files in the SUMMARIES directory tells VPOP3 to keep old MAIL.LOG files in the VPOP3\SUMMARIES directory instead of deleting them on a weekly cycle. These files are not used by VPOP3, but may be used for your own analysis.

As well as the daily summary reports, you can generate some reports as needed from the Reports section of the administration console.

By default VPOP3 writes failed login attempts, password changes, etc to a log file called Security.log in the VPOP3 diagnostics.

If you check the Security log contains successful logons box, then VPOP3 will also record successful logins to the security.log file.

The historical logging setting tells VPOP3 to record details about messages sent/received. This uses resources, but allows message reports to be generated over time.

The Enable Historical Logging checkbox enables logging of the data

The Store Historical Logging Data for option tells VPOP3 how long to keep the data for before it is removed from the database. (Once it has been removed from the database it cannot be recovered, unless you have a database backup)

The Log Database Status section contains information about the Historical Logging database, such as whether it is active or not, and how many entries are currently queued up to be written to the database.