Mail Server Monitor - Troubleshooting
Common Mail Server Monitor Errors and Troubleshooting Guide
1. Unknown Host Error
- Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution problems, incorrect mail server configurations, or network-related issues.
- Possible Causes:
- Incorrect Server Address: The hostname provided for the mail server might be incorrect.
- DNS Resolution Failure: The DNS server cannot resolve the provided hostname to its corresponding IP address.
- Firewall or Security Restrictions: Firewalls or security software block DNS queries or access to the mail server.
- Troubleshooting:
- Ensure mail server hostname provided is correct.
- Run ping command and ensure mail server host is accessible from Applications Manager installed server.
- ping <mailserver_host>
- Verify that no VPN, proxy, or network restriction is causing connectivity issues.
- Ensure firewalls or antivirus software is not blocking the server access.
2. Connection Refused/Unable to Connect/Connection Timeout
- Description: The "Connection Refused/Unable to Connect/Connection Timeout" error occurs when a mail client (such as an email app or server) cannot establish a connection to the mail server. This error usually indicates that the mail server is either unreachable or has rejected the connection attempt outright.
- Possible Causes:
- Server is Down or Unreachable: The mail server might be offline, undergoing maintenance, or experiencing network issues.
- Incorrect Server Address or Port: The client may be configured with the wrong hostname, IP address, or port number, preventing a successful connection.
- Firewall or Security Software Blocking the Connection: Firewalls, security software, or network policies may block access to the mail server’s ports.
- Protocol Mismatch: The client might be trying to connect using the wrong protocol (e.g., using POP instead of IMAP).
- Server Load or Connection Limits: If the server is handling a high number of requests, it might temporarily refuse new connections until resources become available.
- Troubleshooting:
- Check Server Status: Ensure the mail server is online and reachable.
- Verify Server Address and Port: Confirm correct hostname and port for SMTP, IMAP, or POP.
- Review Firewall/Security Software: Check that firewall or security settings allow the connection.
- Confirm Protocol: Ensure correct protocol is selected for IMAP/POP configurations.
- Proxy configuration: Check if any proxy configuration is required for connecting to mail server.
- Timeout: Try increasing the timeout and try again.
3. Unsupported or unrecognized SSL message
- Description: This error indicates a failure in establishing a secure (SSL/TLS) connection between the mail client and the server. It typically occurs when the client attempts to use SSL/TLS on a server or port that does not support it, or when there is a mismatch in protocol configurations.
- Possible Causes:
- Incorrect Port Configuration: The client is configured to use SSL/TLS on a port that does not support it.
- Non-SSL/TLS Enabled Server: The mail server does not support SSL/TLS or has it disabled for the selected port.
- SSL/TLS Certificates issue: The server’s SSL/TLS certificate is invalid, expired, or misconfigured.
- Troubleshooting:
- Ensure the correct port and protocol were selected.
- Below are the default SSL/TLS ports for Mail server
- SMTP with SSL/TLS: Port 465
- IMAP with SSL: Port 993
- POP3 with SSL: Port 995
- If TLS is enabled, Select TLS Enabled option.
- Try adding the Mail server monitor with SSL/TLS option disabled and providing non-SSL port.
4. Unexpected error
- Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution problems, incorrect mail server configurations, or network-related issues.
- Possible Causes:
- Incorrect Server Address: The hostname provided for the mail server might be incorrect.
- DNS Resolution Failure: The DNS server cannot resolve the provided hostname to its corresponding IP address.
- Firewall or Security Restrictions: Firewalls or security software block DNS queries or access to the mail server.
- Troubleshooting:
- Ensure mail server hostname provided is correct.
- Run ping command and ensure mail server host is accessible from Applications Manager installed server.
- ping <mailserver_host>
- Verify that no VPN, proxy, or network restriction is causing connectivity issues.
- Ensure firewalls or antivirus software is not blocking the server access.
New to ADSelfService Plus?
Related Articles
Real User Monitor (RUM) - Troubleshooting
If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...
Troubleshooting URL Monitor
Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...
DNS Monitor - Troubleshooting
Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...
PHP Monitor Troubleshooting
PHP Monitor Errors and Troubleshooting Guide Check if the phpstats.php file in the webserver's document root. Ensure there is no modifications done in phpstats.php file Check if the correct PHP path is given. Retry with the "SSL is enabled" option ...
REST API Monitor - FAQS
1. What should I do when Basic Authentication fails in REST API monitor? Verify if the credentials provided in the Applications Manager are correct. Try if sending username and password in Authorization request header works Get an BASE-64 encoded ...