Contents

Introduction

Prerequisites

When should I enable limittrackingevents?

What happens when I enable limittrackingevents?

How do I enable limittrackingevents?

Introduction

This document describes what the limittrackingevents feature on an Email Security Appliance (ESA) is and how to enable it.

Prerequisites

- ESA running AsyncOS 11.0.1-301 or newer. For supported versions, you can refer to CSCzv32858.

When should I enable limittrackingevents?

The limittrackingevents feature is recommended when the ESA is impacted by CSCzv32858. This defect causes the message tracking to encounter memory consumption issues from too many events being inserted into the tracking database.

What happens when I enable limittrackingevents?

This feature will truncate any excessive events that are being parsed into the tracking database.

Limited events are as follows:

- URLs matching a WBRS filter rule are limited to 20

- URLs being rewritten are limited to 20

- URLs being rewritten for VOF are limited to 20

- Recipients on an email are limited to 50

- Recipients delivered are limited to 50

- Bounces are limited to 50 per email

- Failed responses from a remote server during injection are limited to 5

- Start delivery attempts per MID are limited to 5

How do I enable limittrackingevents?

From the CLI, limittrackingevents can be enabled under trackingconfig. Ensure to commit and save your changes.

Note:  limittrackingevents is a hidden sub-command of trackingconfig so you will not see the option available.

esa.local> trackingconfig

Message Tracking service status: Message Tracking is enabled.

Choose the operation you want to perform:

- SETUP - Enable Message Tracking for this appliance.

[]> limittrackingevents

Limit tracking events?

Currently no events are being truncated.

Would you like enable Tracking Events to be truncated? [N]> Y

Choose the operation you want to perform:

- SETUP - Enable Message Tracking for this appliance.

[]>

esa.local> commit