dudescholar

I solved this problem using a jailshell. See the following discussion: http://www.totalchoicehosting.com/forums/i...?showtopic=3402 It could be solved with any shell access you might have where port 25 is not blocked. Unfortunately, the jailshell was somehow disabled and I need to get it enabled again. I intend to configure my mail reader to read mail via ssh as well so that my passwords etc. always go ever the interent encrypted instead of "in the clear". Today it appears that cox cable has started blocking port 119 (nntp) keeping me form accessing a service I've paid for and used for many years. Now I need to configure something that bypasses that blocking as well. -- dudescholar

I slept on it and the problem is solved. I needed to authenticate myself to the smtp server. Since I wasn't doing that in my email program, the smtp server was only letting me send locally within my domain. I suspect that any name and password for one of my email accounts will work but I used the name that was given me by totalchoicehosting when my original account was set up. Steve (dudescholar)

OK, support set me up with a jailshell. Here is what I tried that worked, somewhat, but only for email recipents in my domain. First, on the linux side I typed the command (my domain is basicmail.net): ssh -f -l basicma basicmail.net -L 2525:mail.basicmail.net:25 sleep 99999 The -f allows ssh to ask for my password and then puts it self in the background. The sleep 99999 keeps the connection open for my testing - its running on the server. In my mail program "KMail", I set the smtp host to localhost and then set the local port to connect too to 2525 as configured above. If I am sending to an email address in my domain - some_email_name@basicmail.net, it works bypassing my local ISP and connecting to mail.basicmail.net. If the receipent is not in the basicmail.net domain, it fails. Right now I'm going to sleep on this and see what I can come up with. I'm not sure why it should fail if I send to an email address like dudescholar@yahoo.com. -- Steve (dudescholar)

Actually your local ISP won't see your port 25 request. For example, one of my domains is basicmail.net and I would like to use smtp.basicmail.net on port 25 on basicmail.net to send mail. If I had access to a standard shell on basicmail.net (I'm not sure about a jailshell) I could log in and send mail OR I could set up a secure shell from my local machine to basicmail.net and when ever I tried to send mail on a port 25 it would get forwarded over the ssh link and send on the remote host - basicmail.net in this case. The local ISP would only see an encrypted connect from my machine to the remote machine on a SSH port, they wouldn't otherwise have any access to it. For example, if JailShell would work, here is a command that would do the trick replacing SMTPSERVER, USERNAME, and REMOTEHOST with the correct values: ssh -L 25:SMTPSERVER:25 -L -l USERNAME REMOTEHOST Then, anytime you sent something on port 25, it would pop out at REMOTEHOST and would get there via a SSH port which isn't port 25. I guess the question I have is can one log into a JailShell and sent mail on port 25? If so, then I should be able to build an encrypted pipe using SSH to get there and have mail go down that pipe and pop out at the desired smtp server bypassing the ISP entirely! -- dudescholar

My ISP blocks port 25 so that I have to use their smtp relay. When I'm on the road, I need to reconfigure this each time for each email address - yuck. Is it possible to have a JailShell set up and then use SSH to redirect port 25 for my domain name's smtp relay? That way I'm always correctly configured to send mail when I'm home on my cable modem or on the road and using another ISP. (My ISP used used to block POP3 secure port 995 forcing one to use port 110.) I don't want to pay for JailShell if this isn't going to work - I'll be running Linux and/or windows XP so at my end it's doable. -- dudescholar