NG Firewall sends alert messages in a variety of ways: through ETM Dashboard; via remote syslog to a syslog server; and directly, through its own built-in email daemon.
Alerts generated by NG Firewall are sent to your ETM Dashboard account and can be automatically relayed from there. You can configure various delivery methods for ETM Dashboard's alerts: email, configurable webhooks (including Slack and Pagerduty), and push notifications to our Untangle Go mobile app. See Managing notification profiles to set up your notification profiles.
We recommend using ETM Dashboard's alert relay system as your primary alert delivery method. This article goes into greater detail about setting up this functionality: Creating an alert rule from an event
Remote syslog configuration is found in Config > Admin > Syslog. For more details on setting up remote syslog, refer to: NG Firewall Events Configuration - Syslog.
If email alerts are not arriving in your inbox as expected, this article presents some things you can check on. Note that SMTP email delivery can also be unreliable in and of itself, which is why we recommend using an alternative method whenever possible.
Email server settings
NG Firewall's email daemon is used to send alert messages as well as Reports emails and quarantine notifications. If you have noticed delivery issues with all these features, check your outgoing email server configuration in Config > Email > Outgoing Server.
Outgoing server: cloud hosted email relay
Note: This feature is being removed after version 17.0 and will no longer be supported for all versions.
This option is not recommended. This server has significant limitations: alerts are not delivered in real-time and will be delayed after the initial event. It can also be affected by any connectivity issues preventing your NG Firewall from communicating with that server.
Outgoing server: send directly
This option has no configuration options.
Outgoing server: specified SMTP server
If you are using a specified SMTP server, verify:
- the server address & port setting are correct for your SMTP server
- if the "use authentication" box is checked, verify that the credentials are correct
- that these settings match those on the SMTP server itself
- connectivity to the SMTP server from NG Firewall
- that the SMTP server is accepting email traffic from NG Firewall
If all settings are correct, the issue may be caused by something outside of NG Firewall. In rare instances, there may be a problem with NG Firewall's email daemon.
If NG Firewall is located downstream of another router or firewall — any other device that may be restricting or filtering traffic — it is possible that that device is blocking outgoing SMTP traffic. Check that device's settings to ensure it is not restricting traffic originating from NG Firewall.
In some cases, ISPs themselves may be blocking SMTP traffic. Contact your provider to determine if this is the case.
Email daemon issues
These issues cannot be troubleshot via the NG Firewall GUI. We recommend contacting the ETM Support team for assistance.Follow