I was just about to reply when I read this i thought of the same thing
but using rinetd instead to map local machine port to remote machine
port.   Its also available on the MS platforms (so is SSH by the way).

From http://www.boutell.com/rinetd/
Redirects TCP connections from one IP address and port to another.
rinetd is a single-process server which handles any number of
connections to the address/port pairs specified in the file
/etc/rinetd.conf. Since rinetd runs as a single process using
nonblocking I/O, it is able to redirect a large number of connections
without a severe impact on the machine. This makes it practical to run
TCP services on machines inside an IP masquerading firewall.

For Linux, Windows 95/98/NT.



regards,
Omer,


> -----Original Message-----
> From: LISTSERV site administrators' forum
> [mailto:[log in to unmask]] On Behalf Of William Korb
> Sent: Monday, August 09, 2004 10:20 PM
> To: [log in to unmask]
> Subject: Re: Listserv WA
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Andrew,
>
> I just posed this question myself to L-Soft last month. Their
> official stance is, no, wa & listserv have to be on the same system.
>
> However, I did devise a work-around that allows me to bend
> the rules. My solution might well work for you, too, at least
> if you're running things on a Unix system (or maybe on
> Windows, even, but I'd have no idea how).
>
> The wa cgi program sends requests to the listserv daemon over
> a socket at TCP port 2306. It expects that the daemon is
> running on the same server, and there is no way to
> reconfigure it (I asked about a /etc/lsv-wa.config setting,
> but was told there isn't one).
>
> What I did is this: I created an ssh tunnel from my web
> server host to my LISTSERV host that passes port 2306 from
> one machine to the other. Simply run this command on your web
> server machine:
>
> ~ ssh -L 2306:listserv-host:2306 -T -N listserv-host
>
> Where listserv-host is the hostname of the machine that
> you're running the listserv on. When wa connects to port 2306
> on your mail host, it will transparently be forwarded to port
> 2306 on your listserv machine.
>
> Of course, you'll need to add a startup script to restart the
> port forward on reboots.
>
> BTW, this worked for me, but I stress this this is not a
> supported configuration, so caveat emptor.
>
> Good luck!
> Bill
>
> P.S. Not all Unix OSes ship with SSH (and the one that comes
> with Solaris 9 doesn't play well with non-Sun versions of
> SSH, so I don't use it). You can download the source for
> OpenSSH from the official web site, www.openssh.org.
>
> Andrew Bosch wrote:
> | Can WA be run on a separate server from the main Listserv
> | installation?
>
> - --
> William Korb, President & CTO          Phone:  715-382-5462
> QISC, Inc.                             Fax:    715-382-5462
> 19945 82nd Ave., Suite 201             E-mail: [log in to unmask]
> Chippewa Falls, WI 54729-5631          URL:    http://www.qisc.com/
> "Tilting at Digital Windmills since 1995."
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> Comment: What is this gibberish?  http://www.qisc.com/keys/
>
> iD8DBQFBF85uaJBT6t/iy5YRAt4YAJ90pWkacOWKFRX4ObAdwB6pN1q25ACfSE1k
> d9Mgbfc7BeBICrUGFHU2ItY=
> =IJcR
> -----END PGP SIGNATURE-----
>