Thank you very much for the port numbers. They've helped me configure my email clients successfully. If I may, may I ask which authentication system does TCH POP3 servers support, if any? This has boggled me for awhile and is in my email client settings.
Regular - this is a simple authentication mechanism that requires an e-mail client to send a username and password to the server. Username/password data is sent in cleartext form, which could be easily intercepted in transit. This authentication mechanism is supported by most RFC-1081 compliant mail servers, e.g. mail servers that support basic POP3 features.
MD5 &APOP Challenge/Response (RFC-1939) - this authentication mechanism avoids passing a cleartext password over a network. Instead of sending the password as cleartext, the e-mail client sends a non-reversible digest (produced by the MD5 cryptographic hash function) of the password concatenated with a unique random string (Challenge String) received from the server. Any exposure of the digest that is sent during the APOP authentication cycle does not introduce a risk, even for e-mail clients that connect frequently to POP3 servers to check for new mail, e.g. every five minutes. Please note that this authentication mechanism may not be supported by all POP3 servers.
MD5 &CRAM-HMAC Challenge/Response (RFC-2095) - this authentication mechanism is an improvement over the APOP standard. It also follows a Challenge/Response scheme, but uses HMAC (Keyed-Hashing) instead of the simpler digest method. While APOP requires that both the client and server systems have access to the password in cleartext form, HMAC offers a method for avoiding such cleartext storage while retaining the algorithmic simplicity of APOP in using only MD5, though in a "keyed" mode. Another reason to choose Keyed Hashing is the greater security imparted to the authentication of short passwords. Please note that this authentication mechanism may not be supported by all POP3 servers.
Token MD-5 CRAM-HMAC Challenge/Response - this is a hardware implementation of the CRAM-HMAC Challenge/Response (RFC-2095) authentication. A special non-replicable hardware token is used to store the password and to produce the Keyed Hashing. When this authentication mechanism is used, the password will never be exposed at the client side. Once stored, the password cannot be extracted from the token and it is never transferred into the computer where the e-mail client is running. This way, no software (including Spies / Trojan Horses / Viruses) can intercept or otherwise retrieve the password. A mail server administrator may give the user a token that has already had the required password stored on it, so the user won't know and won't need to know the actual password. Utilising the feature that tokens can not be replicated, only the physical owner of the token will have access to the mail server, provided that he or she knows the token's PIN. All POP3 servers that support the MD5 &CRAM-HMAC Challenge/Response (RFC-2095) authentication method support this authentication mechanism.
Also, one of my earlier difficulties made me wonder if it's possible for a symlink creation feature to be added in Cpanel.