Base URL for virtualhosts... again!

Hi guys,
I am a new Mailman user. I run my own server with several virtualhosts on it. I try to figure out, how to change the base URL of lists hosted on my virtualhosts. Every time a new list is created on a virtual host, the default url is set back to the main server again, instead of the virtualhost, hosting that list.
I don't kown a thing about Python. I've already red the previous responses regarding the Base URL question, but couldn't figure how to use fix_url.py Can someone give me a step by step procedure to change to Base URL on some of my lists (not every list) ?
Second question: why did you remove the Base URL attached to each list from the web interface ?
Why use and fix_url script instead ?
One though: as the alias path in the default Apache configuration does not refer to any host in particular, it works with any virtual host (i.e. www.virtualhost1.com/mailman/admin and www.virtualhost2.com/mailman/admin lead to the same admin interface). So why not set the Base URL of a list to the virtualhost on which the list was created?
Thanks for your help.

- When you create a list with "newlist", the info mail sent to the list manager always contains a base URL from the "real" host name of the server. Q: Is there a way to set the base URL and prefered host name of a list at the time of creation? As I said, I am new to this so maybe I just haven't seen the right documentation yet.
That's the question I was asking this morning:
I run my own server with several virtualhosts on it. I try to figure out, how to change the base URL of lists hosted on my virtualhosts. Every time a new list is created on a virtual host, the default URL is set back to the main server again, instead of the virtualhost, hosting that list. Only the email refering to that virtualhost is properly handled on the web pages and in the messages.
Why did the last version of Mailman removed the Base URL attached to each list from the web interface ?
One though: as the Mailman alias path in the Apache configuration does not refer to any host in particular, it works with any virtual host (i.e. www.virtualhost1.com/mailman/admin and www.virtualhost2.com/mailman/admin lead to the same admin interface). So why not set during the new list creation, the Base URL of the new list to the virtualhost on which the list was created?
Jon Carnes explained this morning on the list how to set Mailman to act with two different domains on the same machine. But is the Web URL given in each email message is properly given by Mailman though ?
Michael.

On Tue, 5 Nov 2002 23:22:08 +0100 Michael <info@lashampoo.com> wrote:
- When you create a list with "newlist", the info mail sent to the list manager always contains a base URL from the "real" host name of the server. Q: Is there a way to set the base URL and prefered host name of a list at the time of creation? As I said, I am new to this so maybe I just haven't seen the right documentation yet.
That's the question I was asking this morning:
There is no mention of which version either of you are using. There are things which change from version to version. In a generic way, your questions have been answered. Depending upon which version you're using, your question may have been answered specifically. We are all volunteers, responding to questions as we have the time and as we feel we're able. Have you checked the archives of this list? While you're answering the questions I've asked you and waiting for me to have a few seconds in an already very busy schedule, maybe you can check that out?
-- Raquel
It is only with the heart that we see rightly; what is essential is invisible to the eye. --Antoine de Saint Exupéry

Raquel Rice wrote :
- When you create a list with "newlist", the info mail sent to the list manager always contains a base URL from the "real" host name of the server. Q: Is there a way to set the base URL and prefered host name of a list at the time of creation? As I said, I am new to this so maybe I just haven't seen the right documentation yet.
That's the question I was asking this morning:
There is no mention of which version either of you are using. There are things which change from version to version. In a generic way, your questions have been answered. Depending upon which version you're using, your question may have been answered specifically. We are all volunteers, responding to questions as we have the time and as we feel we're able. Have you checked the archives of this list?
While you're answering the questions I've asked you and waiting for me to have a few seconds in an already very busy schedule, maybe you can check that out?
You're right Raquel, but I was just pointing out the fact many people on this list were looking for the same thing. That's all. I was not yelling or being impatient, and didn't mean to hurt your sensibility. You seem to be very busy indeed. Keep cool Raquel. ;-)
For you question, I'm actually using version 2.1b4
As I said on this list, I've already search the archives for that answer before posting any new question. It seems to have no solution for multi-hosting since version 2.1. The feature "Base URL for Mailman web interface." in the web interface "General Option Sections" seems have been removed in the version 2.1 but was existing in the version previous version 2.0
Or am I wrong ?
Michael.

On Wed, 6 Nov 2002 01:25:00 +0100 Michael <info@lashampoo.com> wrote:
Raquel Rice wrote :
- When you create a list with "newlist", the info mail sent to the >> list manager always contains a base URL from the "real" host name of >> the server. Q: Is there a way to set the base URL and prefered host name of a >> list at the time of creation? As I said, I am new to this so maybe I >> just haven't seen the right documentation yet.
That's the question I was asking this morning:
There is no mention of which version either of you are using. There are things which change from version to version. In a generic way, your questions have been answered. Depending upon which version you're using, your question may have been answered specifically. We are all volunteers, responding to questions as we have the time and as we feel we're able. Have you checked the archives of this list? While you're answering the questions I've asked you and waiting for me to have a few seconds in an already very busy schedule, maybe you can check that out?
You're right Raquel, but I was just pointing out the fact many people on this list were looking for the same thing. That's all. I was not yelling or being impatient, and didn't mean to hurt your sensibility. You seem to be very busy indeed. Keep cool Raquel. ;-)
For you question, I'm actually using version 2.1b4
As I said on this list, I've already search the archives for that answer before posting any new question. It seems to have no solution for multi-hosting since version 2.1. The feature "Base URL for Mailman web interface." in the web interface "General Option Sections" seems have been removed in the version 2.1 but was existing in the version previous version 2.0
Or am I wrong ?
Michael.
Of course, it may have changed from 2.1b3 to version 2.1b4, but you may want to check out "Defaults.py". This is found in the archives. It does not give you the ability to have two list names which are the same, on two different domains however. (You'll have to work with the line lengths below)
# Mailman needs to know about (at least) two fully-qualified domain # names(fqdn); 1) the hostname used in your urls, and 2) the # hostname used in email addresses for your domain. For example, if # people visit your Mailman system with "http://www.dom.ain/mailman" # then your url fqdn is "www.dom.ain", and if people send mail to # your system via "yourlist@dom.ain" then your email fqdn is # "dom.ain". DEFAULT_URL_HOST controls the former, and # DEFAULT_EMAIL_HOST controls the latter. Mailman also needs to # know how to map from one to the other (this is especially # important if you're running with virtual domains). You use # "add_virtualhost(urlfqdn, emailfqdn)" to add new mappings. # # If you don't need to change DEFAULT_EMAIL_HOST and # DEFAULT_URL_HOST in your mm_cfg.py, then you're done; the default # mapping is added automatically. If however you change either # variable in your mm_cfg.py, then be sure to also include the # following: # # add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) # # because otherwise the default mappings won't be correct.
-- Raquel
It is only with the heart that we see rightly; what is essential is invisible to the eye. --Antoine de Saint Exupéry

My original message said I was using 2.0.13
On Tue, 5 Nov 2002 23:22:08 +0100 Michael <info@lashampoo.com> wrote:
There is no mention of which version either of you are using. -- Jeff Donsbach Webmaster and Bass Drummer The Middlesex County Volunteers Fifes and Drums W. Medford, MA

On 11/5/02 5:22 PM, "Michael" <info@lashampoo.com> wrote:
I run my own server with several virtualhosts on it. I try to figure out, how to change the base URL of lists hosted on my virtualhosts. Every time a new list is created on a virtual host, the default URL is set back to the main server again, instead of the virtualhost, hosting that list. Only the email refering to that virtualhost is properly handled on the web pages and in the messages.
Are you adding an add_virtualhost() call for each domain in your mm_cfg.py file?
I had similar problems until I added a domain this way before I created a list in the domain.
- Stoney

Stonewall Ballard wrote :
I run my own server with several virtualhosts on it. I try to figure out, how to change the base URL of lists hosted on my virtualhosts. Every time a new list is created on a virtual host, the default URL is set back to the main server again, instead of the virtualhost, hosting that list. Only the email refering to that virtualhost is properly handled on the web pages and in the messages.
Are you adding an add_virtualhost() call for each domain in your mm_cfg.py file? I had similar problems until I added a domain this way before I created a list in the domain.
Woow! Thanks Ballard.
Yes I had added my domains in my mm_cfg.py configuration but my old lists didn't reflected the changes.
Your trick worked fine. I just had to back up my archives then to remove the lists and create them again to find my problems solved!
Thanks again. Michael.

At 12:39 +0100 11/5/2002, Michael wrote:
Second question: why did you remove the Base URL attached to each list from the web interface ?
If you could do a suitably fuzzy search of the older archives for "a list admin set the Base URL wrong and we can't do anything" you would see lots of posts about variations on that theme. And the unpleasant means of recovery particularly for those lacking heavy-duty access to the server.
It used to be much too easy to create havoc by making a faulty change. Now it's a little to hard to make a correct change.
Seemingly, no one has felt moved to create code that would vette an attempted change and forestall the fatal errors. I don't want to attempt it.
--John
John Baxter jwblist@olympus.net Port Ludlow, WA, USA
participants (5)
-
John W Baxter
-
MCV Webmaster
-
Michael
-
Raquel Rice
-
Stonewall Ballard