Xitoring Document
Home
FAQ
Support
Register
Home
FAQ
Support
Register
  • Xitoring

    • Introduction
    • Release Notes
    • Xitoring Release Notes
    • Linux Xitogent Release Notes
    • Windows Xitogent Release Notes
    • Xitoring Mobile App Release Notes
    • Account Management
    • API Access & Automation
    • Team Management & Collaboration
    • Billing & Subscription Management
  • Getting Started

    • Getting Started with Xitoring
    • Workflows & Guides
    • Monitor Your First Server
    • Import / Migration
    • Migrate from UptimeRobot to Xitoring
    • Migrate from Pingdom to Xitoring
    • Migrate from Uptime.com to Xitoring
    • Migrate from BetterStack to Xitoring
  • Help & Support

    • FAQ & Troubleshooting
    • Glossary
  • Server Monitoring

    • Server Monitoring
    • Graphs
    • Live Statistics
    • Monitor Services
    • Auto-Triggers
  • Xitogent on Linux

    • Install Xitogent on Linux
    • Update Xitogent on Linux
    • Uninstall Xitogent on Linux
  • Xitogent on Windows

    • Install Xitogent on Windows
    • Uninstall Xitogent on Windows
    • Xitogent Service
    • Update Xitogent on Windows
    • Disk Performance (I/O)
  • Xitogent on Azure

    • Xitogent on Azure
    • Monitor Azure Linux VM
    • Monitor Azure Windows VM
  • Xitogent CLI

    • Xitogent CLI
    • Xitogent Pause/Unpause
    • Xitogent Status
    • Xitogent debug
    • Xitogent Diagnosis
    • Which data we collect
  • Xitoring CLI

    • Xitoring CLI
  • Uptime Monitoring

    • What is Uptime Monitoring
    • Monitoring Nodes (Geographic Locations)
    • What is Check
    • Auto-Discovery
    • Auto Fault Tolerance
    • Heartbeat Check
    • Ping Check
    • HTTP(S) Check
    • DNS Check
    • FTP Check
    • SMTP Check
    • IMAP Check
    • POP3 Check
    • TCP Check
    • UDP Check
  • SSL Monitoring

    • SSL Monitoring
  • Incidents

    • Incidents
    • Incident's Root Cause
    • Incidents Notification
    • Incident Notes
    • Resolving Incidents Manually
    • Incident Policy
  • Maintenance Schedule

    • Maintenance Schedule
  • Email Reports

    • Email Reports
  • Integrations

    • Integrations
    • Apache Integration
    • CoreDNS Integration
    • CouchDB Integration
    • Disk Health Integration
    • Docker Integration
    • Dovecot Integration
    • Exim Integration
    • HAProxy Integration
    • IIS Integration
    • InfluxDB Integration
    • Kafka Integration
    • KeyDB Integration
    • LiteSpeed Integration
    • MongoDB Integration
    • MySQL Integration
    • Netstat Integration
    • Nginx Integration
    • OpenLiteSpeed Integration
    • OpenVPN Integration
    • PHP-FPM Integration
    • Postfix Integration
    • PostgreSQL Integration
    • RabbitMQ integration
    • Redis Integration
    • MS SQL Server Integration
    • Supervisor Integration
    • Varnish Integration
    • Wireguard Integration
  • Notifications

    • Notifications
    • Creating Notification Roles
    • Email Integration
    • Mobile Push Notifications
    • SMS Integration
    • Phone call Integration
    • Webhook Integration
    • Integration for Slack
    • Telegram Integration
    • WhatsApp Integration
    • Mattermost Integration
    • Discord Integration
    • Google Chat Integration
    • Microsoft Teams Integration
    • Atlassian Opsgenie Integration
    • Splunk On-Call Integration
    • Pushover Integration
    • Pushbullet Integration
    • Gotify Integration
    • Ntfy Integration
    • Spike.sh Integration
    • PagerDuty Integration
    • Zapier Integration
    • AlertOps Integration
  • Status Page

    • Status page
  • 3rd Party Status Pages

    • Using 3rd party Status Pages
    • Atlassian Status Page Integration with Xitoring
    • Status.io Integration with Xitoring
    • Statuspal Integration with Xitoring
    • Instatus Integration with Xitoring
  • Dashboards

    • Main Dashboard
    • Custom Dashboards
  • Metrics

    • Metrics
  • MCP Server

    • Setup & Tool Reference

IMAP Check

Xitoring's IMAP check enables users to monitor the IMAP service, which is a protocol used for retrieving email messages. The IMAP check can be configured to use different ports, such as port 143, port 443 with STARTTLS encryption, and port 993 with SSL encryption.

To create an IMAP check on Xitoring, users can provide the hostname or IP address of the IMAP server. In the check's settings, users can enable STARTTLS for IMAP services that use port 443, or SSL for IMAP services that use port 993. By selecting the appropriate protocol and port, users can ensure that Xitoring monitors the IMAP service correctly.

Xitoring's IMAP check conducts a comprehensive check on the IMAP service, This ensures that the IMAP service is functioning correctly, and email communication is secure and reliable. If any issues are detected during the check, Xitoring will promptly alert IT, teams, via email, SMS, or other preferred notification channels. This allows IT teams to quickly identify and resolve the issue, minimizing the impact on end-users and protecting sensitive information.

Create IMAP Check

Creating IMAP checks is very easy users just need to enter the correct information and needed configuration to create checks for the IMAP services.

Type

From the list of available check types IMAP will be selected.

Related Server

As in Xitoring, there are Server checks and independent checks, you can Create a check and assign it to a Server so it will count as one of the checks of a specific server. this option also can be changed or edited later.

So the list will contain a list of registered servers that the user can assign the check to them.

Hostname

The hostname is the address of the IMAP check, it can be an IPv4 or IPv6 address or a domain name, you can see examples of each of them in the following box:

IPv4
107.45.66.2

IPv6
fe80::a510:68bd:7405:1869

Domain
xitoring.com

Check Label

Users can choose a name for the check that is being created using this field, Check label can contain characters, space, and numbers. Special characters are not allowed in the check label section.

STARTTLS

IMAP STARTTLS is a protocol that enables secure communication between an email client and an IMAP server. When STARTTLS is enabled, the email client and the server negotiate a secure connection before transmitting any data, preventing eavesdropping and ensuring that the data exchanged is encrypted.

By monitoring the IMAP STARTTLS protocol with Xitoring's IMAP check, IT teams can ensure that the email communication between the client and server is secure. The IMAP check tests the STARTTLS encryption and verifies that the email client can establish a secure connection to the server. If the encryption fails or the connection cannot be established, Xitoring immediately alerts IT teams, allowing them to investigate and resolve the issue quickly.

Port

With the ability to monitor IMAP on different ports, Xitoring's IMAP check can ensure that email communication is secure and reliable, even when using non-standard ports. For example, some email clients may use port 443 for IMAP over TLS to bypass firewalls or for other reasons. By monitoring this port, Xitoring can ensure that email communication remains secure and reliable, regardless of the port used.

Some users might have IMAP services running on different ports, So multiple checks with different ports can be created to make sure that the whole IMAP services are working properly.

Group

The next option is Group. Xitoring has an advanced Group/Sub-Group management system so users can sort and organize Checks and Server, For example, some users organize their assets based on location and create Groups for countries and Sub-Groups for Cities. it can help see the records for a specific part of your assets easily.

Interval

Interval sets how often probing nodes will make their requests to your URL, 1 minute will provide the most detailed, accurate, reports and notifications. Also For some services, the Higher interval makes more sense. So you can configure Xitoring to Check your IMAP Check status every minute or you can make it check every 10 minutes.

Notification Roles

In this section user can assign one or more notification roles to this check trigger, it will define who gets notified and how every time this check has an incident. For Example, the user has two notification roles one for the IT team that contains the Email and phone numbers of the team members, and one notification role for the CTO. Users can configure the trigger to notify the IT team and the CTO in time of an incident using Email and SMS notifications.

Fault Tolerance

Fault tolerance is a time value (Minutes) that determines how much stress can a system take before it's entering a critical state. If you set FT to 5 we send an incident report when the incident is existing for 5 minutes.

Tips

The Run Test button can be used to either determine the current status of the check or make sure that the entered information is correct.

Last Updated: 5/22/23, 2:47 PM
Prev
SMTP Check
Next
POP3 Check