There are a few other things you can do if you've got the time and inclination. For one, you could set up a real VPN between your notebook and another machine, and route all traffic through that. Of course, for it to work on your home computer, you'd need an easy way to find it like dyndns. By doing that with CIPE or IPSec or something, you could not only secure your email, but any other traffic that you don't want getting sniffed. This would also let you use your regular mail clients to read email and not rely on using SSH and text-mode clients.
You could also do port-forwarding with SSH. Your laptop would need to have an SSH client that handles port forwarding, which might be hard with Windows. You'll also need to set up multiple forwards on multiple ports to have it connect to multiple external mail servers, unless you do the fetchmail thing and collect it all on your home machine. -Tim On Tue, 2003-10-14 at 08:16, will hill wrote: > On 2003.10.14 02:21 Shannon B. Roddy wrote: > > I use a service from dyndns.org to solve the ISP DHCP problem. There > > are numerous scripts to update the ISP IP with dyndns. Check it out... > > It works well. You could set up something like Karthik.homeip.net so > > you can always get to your home machine. > > > > Actually, yes my ISP is Cox. However, I have my imap-ssl set up on my > > work machine (which by the way is on a LSU subnet). I just check email > > via my work machine. > > > > Hmmm, sounds like a winner for you Karthik. Get dyndns working, ssh into > your home machine. I'd just run fetchmail and mutt or balsa if the bandwidth > is there. If the bandwidth is not there, you might just sftp your mail spool > to yourself. That will keep people from violating your pop passwords, > especially that Paws account where people can drop your classes and stuff. > > > _______________________________________________ > General mailing list > [email protected] > http://brlug.net/mailman/listinfo/general_brlug.net
