Quote:
so if your isp's smtp server requires secure authentication you have to use stunnel?
|
No, you misunderstood me. Smtps with stunnel is in my office, and I connect to it directly by my mail client. This is a special setup as I mentioned, as an smtps service is usually established without stunnel; using sendmail's built-in capabilities. Anyway, my mail client at home should be able to connect to and authenticate with stunnel listening on the smtps port in my office.
Just a short explanation of stunnel: stunnel can be used to establish a secure (encoded, authenticated) tunnel between two ports. So, you can connect localhost:smtp to oif:smtps by stunnel on your mail server, and you have your smtps service on the outside interface there. Likewise, you connect localhost:http to oif:https with stunnel, and you have secure http service there. The same applies to pop3, too.
Naturally, one could reconfigure sendmail, apache, or qpopper to provide secure services without stunnel, but I found it much more simple to leave those untouched, and just start another stunnel process for any secure service I need (only the related ports need to be changed in the command calling stunnel).