The servers support secure connections for various services, like IMAP and FTP. Non-secure connections typically send your login information in the clear, meaning anyone who is eavesdropping can get your user name and password. For the typical user, the chances of this happening are probably negligible, but with a few simple steps, you can eliminate the possibility altogether.
Modern e-mail clients support secure IMAP, POP3, and SMTP connections. Typically, they will automatically use the correct port numbers. If not, use port 993 for secure IMAP and port 995 for secure POP3. Secure SMTP works on both port 25 and port 465. If port 25 doesn't work for you, it's probably because your ISP blocks that port as part of its spam prevention measures, and you should use port 465 instead.
Although you can get secure SMTP to work with Mysticserver's servers, you may still want to use your ISP's SMTP server. Mysticservers SMTP server uses a self-signed certificate, so your e-mail program will give you a warning about not being able to verify the validity of the certificate. If you're lucky, you can tell your mail client to store the certificate and subsequently always trust it. If not, you'll have to dismiss the warning every time you launch your mail program, in which case, you're probably better off using your ISP's server.
In addition to secure mail connections, you can also establish a secure connection to NetAdmin by using any of the following URLs:
http://yourdomain.tld/securenetadmin
https://yourdomain.tld:2083/
http://servername.mysticserver.com/securenetadmin
https://servername.mysticserver.com:2083/
Using the first two URLs will typically generate a warning about not being able to verify the identity of your domain. This is because the shared SSL certificate is only valid for host names of the form *.Mysticserver.com. Nevertheless, if you ignore the warning, the subsequent connection will be encrypted.
The host name in the bottom two URLs match the SSL certificate; however, if your domain is on adonis, cobalt, hyperion, ichor, juno, metis, oceanus, or pulsar, your browser may still complain about not being able to verify the validity of the certificate. (Your mail application will give you the same warning when it tries to establish a secure IMAP or POP3 connection.) Mysticserver's SSL certificate is signed by Comodo Limited, and Comodo's CA certificate is not typically included with the default set of trusted certicates that comes with your system or software. Ideally, the server should automatically supply it; however, the servers listed above only do so for secure HTTP connections on port 443.
As in the case with the self-signed certificate, you may be able to tell your browser and e-mail program to store the certificate and always trust it. If you can't do this or you'd prefer a cleaner solution, you need to add Comodo's CA certificate to the collection of trusted certificates on your system or in your applications.
Search:
Back
There are no comments on this page. [Add comment]