Using Mailman over SSH-Tunnel
Hi,
I setup mailman to manage lists at xxx@lists.foo.com
The mailinglists works, but the admininterface gives me a headache.
The Webserver is not accessible from the outsite, so I have to use a SSH-Tunnel like ssh -L 8080:localhost:80 me@foo.com
Going to, for example, http://localhost:8080/mailman/private/mailman/listinfo/knownlist, shows me the listinformation for a known list - so far so good. But all links on this page are absolut. The don't use localhost:8080 as base, they all link to http://lists.foo.com/...
This is a big problem, as lists.foo.com is not accessible - the frontend is not usable for me.
Can the scripts be configured, not to use this absolute URLs?
/David
Hello,
On Tue, 28 Nov 2006, Dark Servant wrote:
The mailinglists works, but the admininterface gives me a headache.
The Webserver is not accessible from the outsite, so I have to use a SSH-Tunnel like ssh -L 8080:localhost:80 me@foo.com
Going to, for example, http://localhost:8080/mailman/private/mailman/listinfo/knownlist, shows me the listinformation for a known list - so far so good. But all links on this page are absolut. The don't use localhost:8080 as base, they all link to http://lists.foo.com/...
This is a big problem, as lists.foo.com is not accessible - the frontend is not usable for me.
Can the scripts be configured, not to use this absolute URLs?
You could probably use fix_url.py to change it. But anyway, wouldn't it be better for you to set up a VPN connection to that machine? I do that on a router level and then once I am in, I can use administrative interface on the LAN.
HTH
-- Zbigniew Szalbot
On 11/28/06, Zbigniew Szalbot <zbyszek@szalbot.homedns.org> wrote:
Hello,
On Tue, 28 Nov 2006, Dark Servant wrote:
The mailinglists works, but the admininterface gives me a headache.
The Webserver is not accessible from the outsite, so I have to use a SSH-Tunnel like ssh -L 8080:localhost:80 me@foo.com
Going to, for example, http://localhost:8080/mailman/private/mailman/listinfo/knownlist, shows me the listinformation for a known list - so far so good. But all links on this page are absolut. The don't use localhost:8080 as base, they all link to http://lists.foo.com/...
This is a big problem, as lists.foo.com is not accessible - the frontend is not usable for me.
Can the scripts be configured, not to use this absolute URLs?
You could probably use fix_url.py to change it. But anyway, wouldn't it be better for you to set up a VPN connection to that machine? I do that on a router level and then once I am in, I can use administrative interface on the LAN.
HTH
-- Zbigniew Szalbot
Hm.. what exactly does the fix_url script do? Changing the URLs on the interface as I want? Am I right that setting the DEFAULT_URL_PATTERN to something like " http://localhost:8080/mailman" will work for me, as long people always forward port 8080?
Yes, router level would be nicer, but it should work from any computer and any network - as long as you have ssh access.
David
On 11/28/06, Dark Servant <darkservant@gmail.com> wrote:
Hm.. what exactly does the fix_url script do? Changing the URLs on the interface as I want? It changes the URLs on the pages to match the current config.
Am I right that setting the DEFAULT_URL_PATTERN to something like " http://localhost:8080/mailman" will work for me, as long people always forward port 8080? This isn't exactly right, but you've got the general idea.
- Patrick Bogen
On 11/28/06, Patrick Bogen <pdbogen@gmail.com> wrote:
On 11/28/06, Dark Servant <darkservant@gmail.com> wrote:
Hm.. what exactly does the fix_url script do? Changing the URLs on the interface as I want? It changes the URLs on the pages to match the current config.
Am I right that setting the DEFAULT_URL_PATTERN to something like " http://localhost:8080/mailman" will work for me, as long people always forward port 8080? This isn't exactly right, but you've got the general idea.
- Patrick Bogen
Ok.. after some twiddling, I came up with this configuration: mm_cfg.py: DEFAULT_URL_PATTERN = ' http://localhost:8080/%s/mailman/<http://localhost:8080/%25s/../mailman/> ' add_virtualhost('localhost','lists.foo.com')
I also had to add lists.foo.com/pipermail lists.foo.com/mailman as aliases to http.conf
The virtualhost allows me to create xxx@lists.foo.com lists using the localhost-ssh-tunnel.
That seems to work on first look. Anyone already sees some problems I may face soon?
David
On 11/28/06, Dark Servant <darkservant@gmail.com> wrote:
I setup mailman to manage lists at xxx@lists.foo.com
The mailinglists works, but the admininterface gives me a headache.
The Webserver is not accessible from the outsite, so I have to use a SSH-Tunnel like ssh -L 8080:localhost:80 me@foo.com
Another option might be to use a console-mode web browser, such as elinks. The Mailman pages are pretty simple in their construction, and so elinks should be more than adequate for whatever you need to do.
--
- Patrick Bogen
participants (3)
-
Dark Servant -
Patrick Bogen -
Zbigniew Szalbot