Cisco Cisco Email Security Appliance C160 Mode D'Emploi

sent. The increase is the number of seconds to wait plus twice the last interval. So 
a 5 second wait would have alerts sent at 5 seconds, 15, seconds, 35 seconds, 75 
seconds, 155 seconds, 315 seconds, etc.

Eventually, the interval could become quite large. You can set a cap on the number 
of seconds to wait between intervals via the maximum number of seconds to wait 
before sending a duplicate alert field. For example, if you set the initial value to 
5 seconds, and the maximum value to 60 seconds, alerts would be sent at 5 
seconds, 15 seconds, 35 seconds, 60 seconds, 120 seconds, etc.

Alerts sent from the appliance to addresses specified in the Alert Recipient follow 
SMTP routes defined for those destinations.

To allow IronPort to better support and design future system changes, the IronPort 
appliance can be configured to send IronPort Systems a copy of all alert messages 
generated by the system. This feature, called AutoSupport, is a useful way to 
allow our team to be proactive in supporting your needs. AutoSupport also sends 
weekly reports noting the uptime of the system, the output of the 

status

 

command, and the AsyncOS version used.

By default, alert recipients set to receive Information severity level alerts for 
System alert types will receive a copy of every message sent to IronPort. This can 
be disabled if you do not want to send the weekly alert messages internally. To 
enable or disable this feature, see 

Alert messages are standard email messages. You can configure the Header From: 
address, but the rest of the message is generated automatically.

You can configure the Header From: address via the Edit Settings button or via 
the CLI (see the Cisco IronPort AsyncOS CLI Reference Guide).