How to access a blocked port

Post #386,131 by drook 2/4/14 4:14:19 PM Reply	How to access a blocked port My ISP has mail on a port that is now blocked by my corporate firewall. Is there something I can install on my server (I have shell access) in the same domain as the mail server, that I can connect to over an available port (ie: 80) which will manage the connection to the mail server? -- Drew
Post #386,132 by boxley 2/4/14 4:18:22 PM Reply	your ISP doesn't offer webmail access? Any opinions expressed by me are mine alone, posted from my home computer, on my own time as a free American and do not reflect the opinions of any person or company that I have had professional relations with in the past 58 years. meep
Post #386,138 by drook 2/4/14 4:58:43 PM Reply	Yes, but no filtering that way All my spam rules, sorting, highlighting etc. is in my local client. I should probably look into how to get the spam and other rules onto the server, but the UI for the web client still blows. Hmm ... or look into gmail as a front-end. -- Drew
Post #386,141 by scoenye 2/4/14 7:09:11 PM Reply	SSH port forwarding? Assuming that is the kind of shell access you have and the corp firewall allows it: ssh -L port_local:mail.drook.com:port_remote drook@drook.com Substitute the following: port_local: the number of the port you want the service to appear on port_remote: the remote (now blocked) mail port number mail.drook.com: ISP's mail server name drook@drook.com: your shell access account name Assuming all goes well, you should now be able to point your client at localhost:port_local and retrieve the mail.
Post #386,148 by drook 2/4/14 8:50:46 PM Reply	Will try to set that up I don't have SSH access from work either, so the try/test cycle is going to be pretty slow. -- Drew
Post #386,155 by folkert 2/4/14 11:54:24 PM Reply	Setup SSH to ALSO... Listen on a common alternative HTTP/S port (8080 or 8443 or some such) Then do forwarding from that. -- greg@gregfolkert.net "No snowflake in an avalanche ever feels responsible." --Stanislaw Jerzy Lec
Post #386,160 by drook 2/5/14 12:55:49 AM Reply	Been reading docs and I'm not clear System A: Desktop machine inside Corp firewall. Ports other than 80 (and a few others) blocked. System B: Hosted server, VPS with root shell access. System C: Hosted mailserver, on a non-standard port. What do I set up on system A and what on system B so that I can run a mail client on A picking up mail from C? -- Drew
Post #386,162 by pwhysall 2/5/14 6:46:58 AM Reply	Curveball - would you accept a webmail solution? Can you run up a webmail interface such as Roundcube? Would avoid much farting about...
Post #386,178 by drook 2/5/14 9:47:42 AM Reply	Are there any that learn spam? -- Drew
Post #386,187 by pwhysall 2/5/14 10:37:30 AM 2/5/14 10:39:21 AM Reply	Nah If you've got control of the mailserver, you do that shit in your MTA chain, right? ETA: OTOH, https://github.com/J...in-Mark-as-Junk-2 Edited by pwhysall Feb. 5, 2014, 10:39:21 AM EST Expand All History
Post #386,189 by drook 2/5/14 10:42:14 AM Reply	I don't control the mailserver -- Drew
Post #386,184 by folkert 2/5/14 10:23:34 AM Reply	Re: Been reading docs and I'm not clear This is done from Home or where you have access, Setup your VPS server (System B) to listen with SSH on 8443 (if the allowed outbound from the Corporate firewall). You should use a second "Port" statement, not removing the other ones. `Port 8443` And then try without leaving THAT ssh session. Open a NEW terminal `ssh -p8443 -lyouruser yourhost.yourvps.com` Ensure it is good. Fix if needed. Here is a config example for your Desktop (System A.) This config setups the redirects pointing at your hosted mail server (System C) through you VPS server (system B) greg@omg:~ [0] $ cat ~/.ssh/config Host redirects Hostname yourhost.yourvps.com Port 8443 #Outgoing mail delivery sstmp/esmtps LocalForward 1465 hosted.mailserver.com:465 #Inbound mail pickup (IMAPS) LocalForward 1993 hosted.mailserver.com:993 # Inbound imap, not needed is using imaps LocalForward 1143 hosted.mailserver.com:143 Then just point your mail client at "localhost" or 127.0.0.1 with the proper port for the proper service and it is done. -- greg@gregfolkert.net "No snowflake in an avalanche ever feels responsible." --Stanislaw Jerzy Lec
Post #386,191 by drook 2/5/14 10:43:49 AM Reply	Will try next time I'm at work... home because of snow today -- Drew
Post #386,197 by folkert 2/5/14 1:40:12 PM Reply	You can "try it" at home to verify... It would work. Then just replicate the configs. -- greg@gregfolkert.net "No snowflake in an avalanche ever feels responsible." --Stanislaw Jerzy Lec
Post #386,171 by crazy 2/5/14 9:09:59 AM Reply	tcprelay https://www.google.com/search?q=tcprelay
Post #386,177 by drook 2/5/14 9:47:10 AM Reply	Looks promising, thanks -- Drew
Post #386,185 by folkert 2/5/14 10:26:59 AM Reply	Not as promising as one might think. It isn't designed for what you are wanting to do... But carry on. -- greg@gregfolkert.net "No snowflake in an avalanche ever feels responsible." --Stanislaw Jerzy Lec

Welcome to IWETHEY!