On Wed, 25 Sep 2002, at 3:36pm, [EMAIL PROTECTED] wrote: > pll@tater:~$ ssh taz -R 8110:199.174.114.33:110 > pll@tater:~$ fetchmail -vc lanminds.com --port 8110 --protocol pop3
*exasperated sigh* My workstation is named DRAGON. Our mail server is named ITCHY. Say the intermediate computer is named LACE (it would be). Like this: DRAGON -------- LACE --------- ITCHY First, on DRAGON, I execute this command: ssh LACE -L 8110:ITCHY:110 That opens up a connection to LACE. It also causes the SSH client to listen on local TCP port 8110. When the SSH client receives a connection on TCP port 8110, it will forward the connection to the SSH server on LACE. The SSH server on LACE will open a connection to TCP port 110 on ITCHY. Next, also on DRAGON, I execute this command: fetchmail LOCALHOST --port 8110 --protocol pop3 That causes fetchmail to connect to DRAGON, on TCP port 8110, using the POP3 protocol. SSH will get that connection, forward it over the SSH tunnel to LACE, and make the connection from LACE to ITCHY. In your examples, you use -R instead of -L, and you tell fetchmail to connect to 'lanminds.com' instead of 'localhost. -- Ben Scott <[EMAIL PROTECTED]> | The opinions expressed in this message are those of the author and do not | | necessarily represent the views or policy of any other person, entity or | | organization. All information is provided without warranty of any kind. | _______________________________________________ gnhlug-discuss mailing list [EMAIL PROTECTED] http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss