Hello,
I see the 'lists' command set to listname-requests keys off the DEFAULT_LIST_ADVERTISED setting in the mm_cfg.py file. Is there any future plans to have the mlist.advertised value come from the actual individual list configurations (e.g., *advertised* option set in the web admin interface under the privacy setting)? As it stands now, the email-based listname-request lists and the web display of lists provide different results (not a big deal, but it has caused some confusion with our staff).
Thanks much!
Jennifer Oxelson sent the message below at 13:14 3/29/2007:
Hello,
I see the 'lists' command set to listname-requests keys off the DEFAULT_LIST_ADVERTISED setting in the mm_cfg.py file. Is there any future plans to have the mlist.advertised value come from the actual individual list configurations (e.g., *advertised* option set in the web admin interface under the privacy setting)? As it stands now, the email-based listname-request lists and the web display of lists provide different results (not a big deal, but it has caused some confusion with our staff).
Thanks much! ---------------- End original message. ---------------------
OK, now that is interesting...
I think I see what is going on, maybe.
I have one public list and three private lists on my server.
If I send the lists command to the request address for the public list, it only responds with the public list.
If I send the command to one of the private list request addresses, it list both the public list and the list I sent it to but not the other private lists.
This is probably somewhat correct behavior because if you know the address for the private list, it should return it. But what is confusing is that the private list shows up under the "Public lists:" header in the response e-mail. I think that this private listing should have a heading in the reply stating that it is private and is listed because of the address used to access the command.
Dragon
Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
Jennifer Oxelson wrote:
I see the 'lists' command set to listname-requests keys off the DEFAULT_LIST_ADVERTISED setting in the mm_cfg.py file.
Where do you see that?
Is there any future plans to have the mlist.advertised value come from the actual individual list configurations (e.g., *advertised* option set in the web admin interface under the privacy setting)? As it stands now, the email-based listname-request lists and the web display of lists provide different results (not a big deal, but it has caused some confusion with our staff).
As Dragon said in his reply, the lists command only lists those lists for which advertised is true with the exception that the list you sent the command to is always listed.
There is another possible reason for the difference. If VIRTUAL_HOST_OVERVIEW is yes (the default), the lists email command will list those advertised lists whose host_name attribute matches that of the list to which the command was sent, whereas the listinfo and admin overview pages will list those advertised lists whose web_page_url attribute contains the hostname of the URL used to access the page. Thus, if there is not a unique mapping between the host in the list's web_page_url attribute and the list's host_name attribute, this can cause the two lists to be different.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Dragon -
Jennifer Oxelson -
Mark Sapiro