Email is one of the most common ways to receive monitoring notifications, because it’s simple, reliable, and works in almost every organization. When something important happens—like a server going down or a threshold being exceeded—an email alert can immediately notify the right people with details about what failed and when. Email is also useful for scheduled reports, so you can review system health without logging into the monitoring dashboard every day.
Email notifications in IPNetwork Monitor. IPNetwork Monitor includes a built-in Send email alert action for status changes and reports. You can use message templates with variables (for example $MonitorName, $CurrentState, and others) so one template works across many monitors. In Email settings, you define the main recipient address (also available as $AdminMail), configure a primary SMTP server (host, port, optional credentials), and choose secure transport such as TLS or SSL when supported. You can also set global From and Reply-To values (with $AdminFrom available in templates), which is helpful when your SMTP server requires the sender address to match its domain. For reliability, you can configure an optional alternate SMTP server that is used automatically if the primary server fails, with its own sender settings and template variable ($AdminFromAlternative).
