Verify that the SmarterMail server is correctly configured to accept connections on the intended ports, using the appropriate encryption protocols, and presenting the correct SSL certificates. This process ensures that mail clients can connect to the server without security warnings or connectivity issues.
Before you begin
You will need:
System Administrator access to the SmarterMail management interface.
Access to the server's command line (e.g., via SSH or RDP).
The specific IP addresses or hostnames used for your mail services.
Verify Port Bindings and Services
Confirm that the SmarterMail services are listening on the correct ports and that the underlying Windows services are running.
Open a command prompt or terminal on the server.
Run the following command to see which ports are listening:
netstat -an | findstr :[PortNumber]
Replace
[PortNumber]with the specific port you are testing (e.g., 25, 465, 587, 143, 993, 995).Verify that the state is
LISTENING.If a port is not listed as listening, ensure the corresponding SmarterMail service is started in the Windows Services manager.
Verify Encryption and Certificate Bindings
Confirm that the server presents the correct certificate and uses the expected encryption method for each protocol.
Use an external tool (such as an online port checker or a command-line tool like
openssl) to test the connection from an outside network.For STARTTLS ports (e.g., 587 or 143), verify the certificate by connecting via a mail client or a testing tool.
For SSL/TLS ports (e.g., 465 or 993), verify that the connection establishes a secure tunnel immediately.
Check the certificate details to ensure the Common Name (CN) or Subject Alternative Name (SAN) matches the hostname used by your users.
Note: If the certificate is self-signed or issued to a different hostname, mail clients may display a security warning or refuse to connect.
Verify SmarterMail Internal Bindings
Ensure SmarterMail is configured to bind these services to the correct IP addresses.
Log in to the SmarterMail administration interface.
Navigate to Settings > Network Settings.
Review the IP Bindings section.
Confirm that each service (SMTP, IMAP, POP, etc.) is bound to the correct IP address or the local loopback address where appropriate.
Save the settings if any changes are made.
Confirm the result
The
netstatcommand confirms the service is listening on the intended port.An external connection test confirms the certificate is valid and the encryption is active.
The SmarterMail administration interface shows the correct IP bindings for each service.
If a port is not responding
Check the Windows Firewall to ensure the specific port is allowed for inbound traffic.
Verify that the SmarterMail service is running and has not crashed.
Ensure that no other software on the server is "squatting" on the port (e.g., a different mail service or web server).
Limitations
This procedure does not verify the validity of the Certificate Authority (CA) chain; it only confirms that a certificate is present and bound to the port. If the certificate is expired or signed by an untrusted CA, clients may still report errors.
