Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Falcone <kevinfal@seas.upenn.edu>
Cc: Harry Putnam <reader@newsguy.com>
Subject: Re: smtp - can it be ssh tunneled?
Date: 19 Dec 2000 16:45:44 -0500	[thread overview]
Message-ID: <m38zpcqe47.fsf@bowline.jibsheet.com> (raw)
In-Reply-To: <m2n1dsuouw.fsf@gnus-5.8.8-cvs.now.playing>

>>>>> "HP" == Harry Putnam <reader@newsguy.com> writes:

  HP> I don't really understand ssh port forwarding but is it possible
  HP> to forward the port that my outgoing mail uses to my ISPs smtp
  HP> port and dump my mail in that way?

If you use smtpmail.el to send mail, then

ssh -L 2525:mail.server:25 shell.server

will point port 2525 on the localhost to 25 on the mailserver,
bouncing it through the shell.server so that it appears that the smtp
conversation is coming from the shell.server.

  HP> Or maybe the opposite way round.  Ssh to the ISP machine then
  HP> forward port 25 to my home machine. And aim sendmail at
  HP> `localhost 25' or something similar.

I do this:

ssh -C -q -L 2525:sierra.seas.upenn.edu:25  blue.seas.upenn.edu

then I twiddled sendmail.cf (not recommended) for the Msmtp Mesmtp
Msmtp8 and Mrelay lines to say localhost 2525 instead of localhost 25

So, gnus invokes sendmail on bowline.jibsheet.com, whose sendmail
relays through sierra.seas.upenn.edu using the ssh port forward from
2525 to 25.

If you want more details, feel free to reply offlist.

-kevin

-- 
"Never go in against a sicilian when death is on the line" 
    -- Vizzini in "The Princess Bride"



  reply	other threads:[~2000-12-19 21:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-19 20:40 Harry Putnam
2000-12-19 21:45 ` Kevin Falcone [this message]
2000-12-19 22:54   ` Harry Putnam
2000-12-19 21:49 ` Kai Großjohann
2000-12-20  0:37   ` Jack Twilley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m38zpcqe47.fsf@bowline.jibsheet.com \
    --to=kevinfal@seas.upenn.edu \
    --cc=reader@newsguy.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).