SMTP Server

Monitor the availability of your SMTP Server and receive instant alerts when the response time crosses the configured threshold. Now you can also monitor your dual stack infrastructure with Site24x7. This is a Basic Monitor.

Add an SMTP Server Monitor

  1. Login to Site24x7.
  2. Click Admin > Inventory > Monitors > Add Monitor.
  3. Select SMTP Server from Add Monitor page.
  4. Specify the following details to add the monitor:
    • Display name: Provide an appropriate name for the SMTP Server which needs to be monitored.
    • SMTP server: Specify the SMTP Host/IP address.
    • Port: Specify the required port number.
      SMTP servers commonly use port 25 for non-secure communications. For SSL/TLS secured Servers, use the port 465.
    • Check Frequency: Choose the required polling frequency. The frequency can be set from 30 seconds  to 1 day. 30 secs can be configured if you're using Enterprise, Enterprise Web, Enterprise Plus Web, Elite, and Elite Web Packs. For all other users 1 minute will be the minimum supported check frequency.
      Configuring 30 seconds check frequency will be consuming the license of two basic monitors.
    • Connection timeout: Specify the time in seconds the connection needs to be established with the target server. 
    • Prefer IPv6: If you want to monitor your SMTP Server over IPv6 enabled locations, simply move the rocker button to "YES" when creating or editing a monitor form.
      • Site24x7 lets you monitor your dual-stacked IPv4/IPv6 based infrastructure as per you need. IPv4 will be enabled as the default protocol. You'll be able to monitor your IPv6 infrastructure, once you enable the rocker button to IPv6. If the connectivity over IPv6 fails, it will not fall back to IPv4 automatically. Read more.
      • Enabling IPv6 in the monitoring form doesn't make it compatible to monitor IPv4, by default. If you want to monitor a resource, which is compatible with both IPv4 and IPv6–you'll have to set up two separate monitor checks for this.
    • Do high availability check mode for better SLA: Enable this option to achieve better SLA reporting for your high availability set-up. In a High Availability environment, monitor will be marked as DOWN only when the connection to all the associated SMTP hosts fail.
      Say, you've multiple SMTP Servers (acting as a High Availability set-up), with both MX records resolving the same IP address. By default, Site24x7 tries to connect to any one of the resolved host to determine the service availability. If connection to any one host fails, the monitor is reported as DOWN. However, when the High Availability check is enabled, Site24x7 attempts to connect to any one available host before marking the monitor as DOWN. It enables you to share better availability SLA data with your customers.
    • Monitoring locations: Select a location profile from the drop down list from where the SMTP Server can be polled from the selected location.
      To know more, refer Location Profile
    • Monitor Groups: You can associate your monitor with multiple monitor groups by selecting the relevant monitor groups from the drop down list. This allows in logical grouping of your monitors. 
      To learn how to create a monitor group for your monitors, refer Monitor Groups.
    • Dependent on monitor: Select a monitor from the drop-down list to choose it as your dependent resource. You can add up to 5 monitors as dependent resources. Alerts to your monitor will be suppressed based on the DOWN status of your dependent resource.
      Configuring a dependent resource and suppressing alerts based on the dependent resource's status is part of providing you with better false alerts protection. Learn more about alert suppression at monitor level.

      If you select "None" in the dependent resource field, alerting will progress as per your normal configuration settings. No alerts will be suppressed in this case as the monitor doesn't have any dependent resource.

      Multiple monitor group support for monitors allow a monitor to be associated with multiple dependent resources in different monitor groups. If during a normal monitor status check, any one of these dependent resources' status is identified as DOWN, the alert for the monitor will be automatically suppressed. However, the dependency configuration at monitor level is always given the higher priority over any other monitor group level dependency configuration for suppressing alerts.
  5. Specify the following details for Configuration Profiles:
    • Threshold and Availability: Select a threshold profile from the drop down list or choose the default threshold set available and get notified when the resources cross the configured threshold and availability.
      To create a customized profile, refer Threshold and Availability.
    • Notification Profile: Choose a notification profile from the drop down list or select the default profile available. Notification profile helps to configure when and who needs to be notified in case of downtime.
      Refer Notification Profile to create a customized notification profile.
    • User Alert Group: Select the user group that need to be alerted during a outage.
      To add multiple users in a group, see User Alert Group.
    • Tags: Associate your monitor with predefined Tag(s) to help organize and manage your monitors creatively. Learn how to add Tags.
    • IT Automation: Select an automation to be executed when the website is down/trouble/up/any status change/any attribute change. The defined action gets executed when there is a state change and selected user groups are alerted.
      To automate corrective actions on failure, refer IT Automation.
  6. Third Party Integrations: Associate your monitor with a pre-configured third-party service. It lets you push your monitor alarms to selected services and facilitate improved incident management.
    If you haven't setup any integrations yet, navigate across to ”Admin > Third Party Integration” to create one. Tell me more.
  7. Click Save.

Learn more about the various performance metrics of a SMTP Server Monitor.

Was this document helpful?
Thanks for taking the time to share your feedback. We’ll use your feedback to improve our online help resources.