Ahhh - yes that is always a problem with shared hosting of any kind due to shared IP addresses.
To be clear on the Tsohosting cloud and cpanel shared hosting SSL is available for mail but either:
a. You configure your email client to use their hostnames (mail.tsohost.co.uk or somesuch)
b. You configure your mail client to use mail.yourdomain.co.uk / smtp.yourdomain.co.uk and the first time you send or receive you get a warning about the certificate being for another host (TSO's servers). Most sensible mail clients allow you to review and permanently accept the so called "security exception". Thereafter, no more warnings.
This is unavoidable with shared hosting. It is simply due to how the SSL protocol and cetification works. Let's take a worked example:
1. You configure your email client to send via smtp.yourdomain.co.uk with SSL on port 465 and send a mail
2. Your email client requests a DNS lookup for smtp.yourdomain.co.uk that resolves back to the IP address of TSOhost's mail cluster
3. Your email client connects to that IP on port 465 and asks "Hey, I need an SSL connection. Send me your public key, your preferred encryption method and any certification details."
4. At this point the mail server only knows that a client needs to connect using SSL (in fact at this point the mail processes on the server are not involed, it is just the SSL process) - it has no way of knowing what domain will need to be accessed so can only be configured to return the certification for mail.tsohost...
5. Your mail client throws a warning
6a. You accept the warning and store the exception then carry on
6b. You think GCHQ / NSA / Other nefarious actor is trying to intercept your mail, don a tinfoil hat and become a recluse
Quite simply, email is not secure. Even if you SSL between yourself and your provider there is no guarantee that any further hops toward delivery are under SSL (most MTA to MTA connections are not), even if they are any intermediary hop and the mail servers at each end have the mail in clear text whilst it is being transited and possibly for some time in logs.
If you want to secure the content of your mail use GPG or PGP, but that still won't hide what mail addresses email is passing to and from (commonly known as Signals Intelligence SIGINT).
With PRISM, ECHELON, TEMPORA etc. in place it's pretty much a given that mail contents are being analysed en masse.
Hmmm... how did I get here, went off on a ramble, I blame the beer. SSL for mail will protect your password from being sniffed between you and your provider which is probably what 99.999% of people bother to think about it for. For anything else beyond that...
edit to say - sorry I meant to addendum that ramble with something about how once you look into all that capitalised stuff above you come to the conclusion that email as it is cannot be secured, it was never designed from the outset to be secure and all the sticky plasters of SSL/TLS, ESMTP, S/MIME etc. that have come and gone can't address that - they're like the fool trying to build a castle on sand. Certificated SSL via the likes of Verisign, Thawte, RapidSSL et al. (for web or email) can be easily compromised with the right court order and a MITM (man in the middle) box. We simply have to accept that sending email is like sending a postcard, anyone can read it including the postman and anyone who slips the postman a fiver.
eek - even the edit went off on a ramble, sorry about that. Anyway, if you are at all concerned beyond protecting your password get reading and educate yourself on the decades old question of how to form trust relationships on the internet - many books mave been written on this but still we don't really have a workable solution.
Sleep well citizen.
Edited by deleted (Sat 17-Aug-13 01:56:47)