![]() Where "" is the IP address of the IMAP server and "hostname" is the hostname/IP address of the SSH server. All you have to do is:\n ssh -N -f -L1430::143 hostname With an SSH tunnel, it is secure like an SSL connection, but it is set up once, and stays up, probably until one of the systems is rebooted. This would create a significant amount of overhead. Of course, SquirrelMail is less than optimal when it comes to IMAP connections (it makes a new one for every IMAP request). The reason is that if you just wrap both ends in Stunnel, you have to setup an SSL connection, do your little IMAP request, then tear down the SSL connection. If your servers are separate or if you must force encrypted communication to your IMAPS server, try using Stunnel, creating an SSH tunnel or using VPN. If your mail server is the same as your web server, there is no need for the encrypted communication. ![]() The biggest downside with Stunnel is the amount of overhead to establish a secure connection to the IMAP server, especially when we hit the IMAP server so frequently (nearly every page click). Stunnel allows to add SSL support to client that doesn't support SSL. ![]() If you can't use PHP with the OpenSSL extension, try tunneling SquirrelMail through Stunnel. More information can be found in doc/authentication.txt and SquirrelMail Administrator's Guide. It requires SSLv3 or TLS support on SSL enabled server. ![]() IMAP over SSL uses 993 port, SMTP over SSL uses 465 port. If you are running PHP 4.3 or later with the OpenSSL extension, then run SquirrelMail configuration utility ( ), enable Secure TLS option in IMAP or SMTP configuration and set port settings to use IMAP or SMTP over SSL ports. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |