On 10:21 AM 10/21/2001 -0400, Charlie Summers wrote:
>I can't use my own secured server to send mail while on the road
I find it depressing that someone who manages mailing lists and has their
"own secured server" resorts to this lame excuse. If it's your own secured
server you have many different ways to authenticate yourself and send thru
it, including (but not limited to):
SMTP Auth (only works if your network connection doesn't hijack port 25 as
is unfortunately becoming increasingly common on lame consumer networks)
Pop before send (same port 25 access issues as above)
UsePopSend/pop rcpt (my ISP supports that and so that's how I pop and send
all my personal email, no need for any SMTP server to connect my client
to) This works anytime you can POP your email on port 110, no need to use
port 25 from your client computer AT ALL.
SSH to the server and setup a port 25 tunnel from your computer to the
server, then send your email thru the SSH tunnel. Port tunneling via SSH
is supported by a large number of SSH clients. Your mail gets sent
encrypted (that's how I POP ALL my email from servers that don't support
POPS, that way I can safely POP email from an insecure network such as the
wireless LAN at conventions, as I'm doing today at nanog) and over the SSH
tunnel, so the mail server sees the port 25 connection as originating from
itself. Assuming you already have SSH access to your own secured server,
you shouldn't need to configure anything different on your server or your
client for this to work, you just need to start the SSH tunnel before you
send email. IMHO that's a whole lot easier than changing your SMTP server
settings on your client depending on where you are connecting from at the
moment. This works anytime you can SSH on port 22, which is almost all the
time.
jc
References:
|
|
