Purging archives
These settings determine how frequently archives are deleted. By default, they are never archives are never purged. If you like to conserve disk space in your server, you may change these settings.
Purging archives settings do not apply to transactional messages.
The fields available are explained in the table below:
| Field Name | Description |
|---|---|
|
Keep Archived Messages for How Many Days |
This setting determines how long archived messages are saved. Saving a message in the archives allows it to be read at a later date By default, your list is set to 0 (zero), or to keep archives indefinitely. If you set the list to not keep archives, no archives is ever going to be saved. This is the opposite of setting the list to 0 (zero). Not saving archives conserves disk space. Note If you disable archive saving completely, users can no longer be able to receive digest versions of the mailing list, and duplicate messages is not going to be removed. If you want your users to be able to receive digests, but do not want to keep archives, set the Archive Messages to Enable Merge Mailings setting to Yes and set Keep Archived Messages for How Many Days to 1. For more information, see Enable Features |
|
Keep How Many Messages Archived |
This setting determines how many messages from the list are to be saved in the archives. For example, a setting of 10 means that the previous 10 messages are saved in the archives. Any old messages beyond the most recent 10 messages are automatically removed By default, your list is set to 0 (zero), or to keep archives indefinitely. If you set the list to not keep archives, no archives is ever going to be saved. This is the opposite of setting the list to 0 (zero) |
|
Keep Mailing and Clickthrough Data for How Many Days |
This setting determines how long outgoing mailing campaigns to your list are saved. Granular per-member delivery and clickthrough data is only available for saved mailings. If you are going to need to refer to this data in the future, increase this setting Note This setting plays an important role in controlling the growth rate of your database. Also server performance may decline if you keep mailing and clickthrough data for a very long time for many of your lists When choosing a setting, you should consider how far back you plan on targeting mailings based on receipt of previous mailings or on clicks and opens . If you do not plan on targeting members using these metrics it may be wise to cap your database growth rate by selecting a value such as one year, also keeping in mind that the longer certain metric data is kept the less relevant it may become to you based on your individual business goals. By default, Aurea List Manager does not purge aggregated statistical data on mailing and click/open trends so that information is still be available to you under the reporting section of Aurea List Manager to help you guide your mailing campaign decisions. It is important to be aware that large databases can become difficult to back up and restore in case of an emergency, which can increase your downtime in the event of a systems failure. Large databases are also difficult to move between servers, making upgrades more painful. We recommend keeping an eye on your database growth rate based on your sending volume. If you are a high volume sender mailing to millions of recipients per month you are going to have a high growth rate, but if you are a low volume sender, your database grows at a slower pace. If you are a systems administrator you may wish to monitor your database using tools of your choice and encourage list administrators to cap mailing data collection based on what you are comfortable supporting. If you are a list administrator noticing declined systems performance, you may want to make your systems administrator aware so that a database size policy can be implemented. |