Build a mail connection checklist This is a checklist, not a confirmed diagnosis or a fixed connection. https://cyber-tool.org/en/port/995#mail-guide Incoming · POP3 · 995 995: POP3 with TLS from the start (SSL/TLS). This setting is not for sending mail. Incoming · IMAP · 993 993: IMAP with TLS from the start (SSL/TLS). Obtain the incoming hostname from your provider. Outgoing · SMTP · 587 587: message submission to an outgoing server. Use the provider’s STARTTLS setting; do not continue unencrypted if TLS fails. Outgoing · SMTP · 465 465: SMTP submission with TLS from the start. Do not mix this with 587/STARTTLS settings; use the option your provider supports. Cannot connect / timeout Compare the hostname and port with your provider’s current incoming or outgoing settings. Check from the device or application network where the failure occurs. VPNs and organizational networks may use a different path. A timeout alone does not prove firewall blocking. Check name resolution, the network path and service availability separately. TLS / certificate error Compare TLS from the start on 995, 993 and 465 with the provider’s STARTTLS setting on 587. Check the certificate hostname, device clock and trust chain; keep certificate verification enabled. An open TCP port does not establish a successful TLS handshake or certificate validation. Sign-in / authentication error Confirm the intended provider, account type and server. Check whether the client supports the required modern sign-in method and whether the account permits the protocol. Do not automatically repeat failed logins; use a redacted version of the error when seeking help. Connected but mail is missing / not delivered Separate receiving from sending and examine the matching server settings. Check the client error code and provider service status; a TCP result does not establish mail delivery. Keep subjects, message bodies, recipient addresses and raw mail headers out of public support tickets. Provider comparison: hostname + protocol + port + TLS mode + sign-in method must match. Using the Outlook desktop app does not mean the account is hosted by Outlook.com. Other provider / organizational mail: use the hostname and sign-in method supplied by the administrator. The MX record need not be the IMAP/POP/SMTP submission hostname used by a mail client. Personal Gmail: use “Sign in with Google” in a supported client. Google Workspace accounts may have administrator restrictions. Outlook.com accounts: check Microsoft’s current OAuth2/Modern Auth and POP/IMAP access requirements. Do not assume Microsoft 365 organizational accounts use the same setup. Support summary: protocol/port, failure stage, network used for the check and a redacted error code. Incoming mail: compare webmail with client folders, filters and synchronization settings. POP3 and IMAP do not offer identical folder synchronization behavior. Outgoing mail: acceptance by a submission server does not prove inbox delivery. An authorized administrator should inspect the provider queue and bounce code; do not send automated test mail. RFC 8314: TLS for mail: https://www.rfc-editor.org/rfc/rfc8314 RFC 6409: submission: https://www.rfc-editor.org/rfc/rfc6409 Gmail client setup: https://support.google.com/mail/answer/7126229?hl=en Outlook.com settings: https://support.microsoft.com/en-us/outlook/pop-imap-and-smtp-settings-for-outlook-com Windows Test-NetConnection: https://learn.microsoft.com/en-us/powershell/module/nettcpip/test-netconnection OpenBSD nc: https://man.openbsd.org/nc