1 |
On Mon, Feb 18, 2008 at 07:26:28PM +0000, Penguin Lover Mick squawked: |
2 |
> > ssh -p 443 -L 2222:smtpserver:25 me@remote_sshd.com |
3 |
> > |
4 |
> > and configure your mail client to send to localhost, port 2222. |
5 |
> > Another alternative (depending upon how many ports you need to forward) |
6 |
> > could be to use SOCKS. |
7 |
> |
8 |
> With option -D on the server. Hmm, need to explain that the ssh server is NOT |
9 |
> the mail server (and last time I looked gmail did not accept ssh connections |
10 |
> to their mail servers!), but a router I run at home. The idea is that I will |
11 |
> set up corresponding forwarding rules on the router. Is that sound? |
12 |
|
13 |
Does your mail server at home have a real ip address? You can do |
14 |
|
15 |
ssh -l <username> -p 443 -N ssh.server.address -L localport:mail.server.address:remoteport |
16 |
|
17 |
And you don't need to worry about setting up forwarding rules on the |
18 |
router. |
19 |
|
20 |
It might even work with private ip addresses for the mail server (I've |
21 |
never tried that... but it could be true that the ssh server will try |
22 |
to look up the ip address of mail server relative to where it is |
23 |
sitting, in that case it should be possible to address something |
24 |
behind an NAT). |
25 |
|
26 |
W |
27 |
-- |
28 |
Pintsize: Hehe, yeah, that does sound like a pretty empty, pointless |
29 |
existence. |
30 |
Marten: You are not helping, you know. |
31 |
Pintsize: Wait, I'm supposed to be HELPING? |
32 |
Sortir en Pantoufles: up 437 days, 20:52 |
33 |
-- |
34 |
gentoo-user@l.g.o mailing list |