D-Link NetDefendOS

6. The event counter is reset to zero and event counting within the Event count period begins
again.
Sending Test Emails
The mail alerting feature has a Send Test Email function to send a test email to the server. This is
done by pushing the Send test email button in the Web Interface. In the CLI, a test email is sent
with the following command:
gw-world:/> smtp -sendmail -logreceiver=<mail-alerting-object-name>
The body of the test email will contain text which is similar to the following:
This is message #1 sent to test the Mail Alerting object "my_mail_alert"
The number "#1" in the message will increment every time a test mail is sent from this log
receiver.
In the Web Interface, the test button can be pushed even while the Mail Alerting object is being
created and before the configuration change is activated and saved. This is not true with the
equivalent CLI test mail function.
Sending to Multiple Email Addresses
More than one Mail Alerting object can be created so that log messages are sent to multiple
email addresses. However, if the same log message information is being sent to multiple email
addresses then it is not recommended to create multiple Mail Alerting objects for this purpose.
Instead, create a mailing list email address on the SMTP server so that a mail sent to that address
is sent to multiple email recipients.
Mail Size Limit
In order to limit the available memory that NetDefendOS uses for buffering log messages and
building the email body, a limit is set on the email size. This limit is 8 Kbytes. When this limit is
reached but the email had not yet been sent, any new log messages will be dropped. If events
are dropped, the following message added to the email body:
message(s) have been discarded because of because of email body size limit
If the available memory is completely used up while building the email, this message will have a
slightly different text to indicate that. If message are dropped repeatedly, it is an indication that
either the event filter should be made more restrictive or that the emails should be sent more
often.
If more than one Mail Alerting object is created, each will have its own piece of memory allocated
for building emails.
Example 2.30. Setting up a Mail Alerting Object
This example configures an Mail Alerting object called my_smtp_receiver so that all events with a
severity equal to Emergency or Alert are sent out in an email.
It is assumed that the recipient email address is admn@example.com and that the SMTP server
address is 203.0.113.10. The default values for the threshold and associated properties are used.
Chapter 2: Management and Maintenance
95