FAQ
Hi,

I've been running a mailman list for about a year and the time has
come to switch servers. I've started off by setting up a new mailman
installation but have run into some problems. 1) Any list I create
through the command line bin/newlist isn't accessible through a web
browser (There's the No Such List error) and 2) Despite resetting the
site password and list creator password a few times, I can't create a
new list through a web browser.

I've tried editing data/sitelist.cfg and setting advertised =1 and
then using config_list to reset the list configuration. I've fiddled
with the DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in mm_cfg.py and
poked around FAQs and documentation online for a long time. I've also
tried just tarring up the existing working mailman directory and
moving it over to the new machine, but alas, that had the same issue.
I tried setting up another installation on a different machine (all
machines are Red Hat Linux, Apache 2), same problem. bin/list_lists do
list the lists that were created from the command line.
VIRTUAL_HOST_OVERVIEW is still set to On in Default.py.

I thought there might have been an issue with the hostname having a
uppercase letter in it, while the HTTP_HOST is all lower case, but I
recompiled using --with-mailhost and --with-urlhost to use the
lowercase name and still had the same problem, and have changed the
settings in mm_cfg.py and used add_virtualhost.

Any suggestions would be appreciated.

Travis

Search Discussions

  • Mark Sapiro at Mar 17, 2006 at 2:54 am

    Travis Derouin wrote:
    I've been running a mailman list for about a year and the time has
    come to switch servers. I've started off by setting up a new mailman
    installation but have run into some problems. 1) Any list I create
    through the command line bin/newlist isn't accessible through a web
    browser (There's the No Such List error) and 2) Despite resetting the
    site password and list creator password a few times, I can't create a
    new list through a web browser.

    And what's the error message for that?

    I've tried editing data/sitelist.cfg and setting advertised =1 and
    then using config_list to reset the list configuration. I've fiddled
    with the DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in mm_cfg.py and
    poked around FAQs and documentation online for a long time. I've also
    tried just tarring up the existing working mailman directory and
    moving it over to the new machine, but alas, that had the same issue.
    I tried setting up another installation on a different machine (all
    machines are Red Hat Linux, Apache 2), same problem. bin/list_lists do
    list the lists that were created from the command line.
    VIRTUAL_HOST_OVERVIEW is still set to On in Default.py.

    I thought there might have been an issue with the hostname having a
    uppercase letter in it, while the HTTP_HOST is all lower case, but I
    recompiled using --with-mailhost and --with-urlhost to use the
    lowercase name and still had the same problem, and have changed the
    settings in mm_cfg.py and used add_virtualhost.

    Any suggestions would be appreciated.

    Read this FAQ
    <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.029.htp>.
    Do not overlook the section on "Existing versus new lists"

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Travis Derouin at Mar 17, 2006 at 3:24 am
    Hey Mark,

    I get the standard

    Error: You are not authorized to create new mailing lists

    error when trying to create a new list through the browser, despite
    setting the both the site password and list creator password to
    something simple like abc123 with mmsitepass.

    I did go through that FAQ a few times today, and tried out the
    different suggestions. Even creating a new list from the command line
    has the same problems after changing mm_cfg.py to include the 2
    hostname specifications. It's odd because in my current installation
    I'm just using the usual hostname for the server, with no virtual
    hosts involved.

    Do you have any debugging suggestions? Should I possibly add some
    logging statements to listinfo.py at around line 104 and recompile ?

    There doesn't seem to be any indicitive messages in the logs. Is there
    also any reason why tarring up an existing working mailman
    configuration and swapping hostnames/DNS records might not work
    either?

    Thanks a bunch,
    Travis
    On 3/16/06, Mark Sapiro wrote:
    Travis Derouin wrote:
    I've been running a mailman list for about a year and the time has
    come to switch servers. I've started off by setting up a new mailman
    installation but have run into some problems. 1) Any list I create
    through the command line bin/newlist isn't accessible through a web
    browser (There's the No Such List error) and 2) Despite resetting the
    site password and list creator password a few times, I can't create a
    new list through a web browser.

    And what's the error message for that?

    I've tried editing data/sitelist.cfg and setting advertised =1 and
    then using config_list to reset the list configuration. I've fiddled
    with the DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in mm_cfg.py and
    poked around FAQs and documentation online for a long time. I've also
    tried just tarring up the existing working mailman directory and
    moving it over to the new machine, but alas, that had the same issue.
    I tried setting up another installation on a different machine (all
    machines are Red Hat Linux, Apache 2), same problem. bin/list_lists do
    list the lists that were created from the command line.
    VIRTUAL_HOST_OVERVIEW is still set to On in Default.py.

    I thought there might have been an issue with the hostname having a
    uppercase letter in it, while the HTTP_HOST is all lower case, but I
    recompiled using --with-mailhost and --with-urlhost to use the
    lowercase name and still had the same problem, and have changed the
    settings in mm_cfg.py and used add_virtualhost.

    Any suggestions would be appreciated.

    Read this FAQ
    <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.029.htp>.
    Do not overlook the section on "Existing versus new lists"

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Mark Sapiro at Mar 17, 2006 at 4:13 am

    Travis Derouin wrote:
    I get the standard

    Error: You are not authorized to create new mailing lists

    error when trying to create a new list through the browser, despite
    setting the both the site password and list creator password to
    something simple like abc123 with mmsitepass.

    You're not the first person to complain of this, but I don't have an
    answer.

    I did go through that FAQ a few times today, and tried out the
    different suggestions. Even creating a new list from the command line
    has the same problems after changing mm_cfg.py to include the 2
    hostname specifications. It's odd because in my current installation
    I'm just using the usual hostname for the server, with no virtual
    hosts involved.

    Did you run fix_url on your existing lists?

    Do you have any debugging suggestions? Should I possibly add some
    logging statements to listinfo.py at around line 104 and recompile ?

    First run bin/dumpdb on a lists/listname/config.pck and see what the
    value of the web_page_url attribute is.

    Then, if the list is advertised and the host portion of the url you are
    accessing the listinfo page with matches the host portion of
    web_page_url, the list should appear on the listinfo overview.

    There doesn't seem to be any indicitive messages in the logs. Is there
    also any reason why tarring up an existing working mailman
    configuration and swapping hostnames/DNS records might not work
    either?

    If DNS, etc. is changed so that the installation on the new host is
    accessed with the same names as before, it should work as before.

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Travis Derouin at Mar 17, 2006 at 3:58 pm
    Hey Mark,
    Did you run fix_url on your existing lists?
    Yep, sure did.
    First run bin/dumpdb on a lists/listname/config.pck and see what the
    value of the web_page_url attribute is.

    Then, if the list is advertised and the host portion of the url you are
    accessing the listinfo page with matches the host portion of
    web_page_url, the list should appear on the listinfo overview.
    It's the same, adverised is also set to 1.

    It'd probably be worthwhile for me to debug this a bit. I notice that
    any edits I make to /tmp/mailman-2.1.7/Mailman/Cgi/listinfo.py don't
    show up in src/listinfo when I do a make clean, make , even when I
    introduce syntax errors. Can you let me know how I can introduce some
    debugging statements to get some more info on this problem? I can look
    at the problem creating lists through the web too while I'm at it.

    Thanks,
    Travis
  • Mark Sapiro at Mar 17, 2006 at 5:59 pm

    Travis Derouin wrote:
    It'd probably be worthwhile for me to debug this a bit. I notice that
    any edits I make to /tmp/mailman-2.1.7/Mailman/Cgi/listinfo.py don't
    show up in src/listinfo when I do a make clean, make , even when I
    introduce syntax errors.

    To move python from the unpack/build directory to the installation
    directory, you do

    make install

    but as rich mentions in another post, just edit the Python in the
    install directory and don't bother with make at all.

    Can you let me know how I can introduce some
    debugging statements to get some more info on this problem? I can look
    at the problem creating lists through the web too while I'm at it.

    I suspect this is all going to turn out to be a web browser issue.

    Here's what I'd look at first.

    Check the host name in the heading of the listinfo page. I.e., hostname
    in "hostname Mailing lists'. Is this the same as the URL hostname.

    Then maybe try this patch which will write some stuff to a Mailman log
    named 'debug'.

    --- Mailman/Cgi/listinfo.py 2005-08-26 19:40:15.000000000 -0700
    +++ Mailman/Cgi/listinfo.py 2006-03-17 09:27:43.718750000 -0800
    @@ -65,6 +65,7 @@
    def listinfo_overview(msg=''):
    # Present the general listinfo overview
    hostname = Utils.get_domain()
    + syslog('debug','Hostname from get_domain() = %s', hostname)
    # Set up the document and assign it the correct language. The
    only one we
    # know about at the moment is the server's default.
    doc = Document()
    @@ -85,6 +86,8 @@

    for name in listnames:
    mlist = MailList.MailList(name, lock=0)
    + syslog('debug', 'listname = %s; web_page_url= %s',
    + name, mlist.web_page_url)
    if mlist.advertised:
    if mm_cfg.VIRTUAL_HOST_OVERVIEW and \
    mlist.web_page_url.find(hostname) == -1:


    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedMar 17, '06 at 1:35a
activeMar 17, '06 at 5:59p
posts6
users2
websitelist.org

2 users in discussion

Travis Derouin: 3 posts Mark Sapiro: 3 posts

People

Translate

site design / logo © 2022 Grokbase