Change-Log Keyword

Change-Log= No|Yes[,Yearly|Monthly|Weekly|Single]

This keyword is not available in LISTSERV Lite.

When set to Yes, LISTSERV writes a listname.CHANGELOG file, which contains information about all changes made to individual subscriptions. Commands tracked include subscriptions, unsubscriptions, auto-deletions and all changes to users' personal options. Change-logs must be enabled to produce subscriber activity reports.

The optional second parameter of the "Change-Log=" list header keyword allows list owners to rotate changelogs on a periodic basis (similar to the interval parameter used with list notebooks).

Rotated logs are renamed to listname.CHANGELOG-yyyy[mm[dd|w]].

When the rotation schedule is changed, old logs will be renamed based on the date in the last entry. If the last entry is compatible with the newly introduced period (for example, logs are YEARLY and the last entry is 2001), the log will continue, even if there were also entries for 2000. The definition of the 2001 log is that it contains all the entries for 2001, not that it is the first log started in 2001. Log files are not automatically split or joined together as the schedule is changed, so it's best to decide on a schedule and stick with it.

If the rename fails (for example, because you keep changing the period back and forth), the current log continues.

The changelog reporting features of the web interface only operate on the current changelog.

The default is "Change-Log= No". For backward compatibility, "Change-Log= Yes" is equivalent to "Change-Log= Yes,Single".