I dug around some more and was able to find out how to fix the symptoms. If I run fix_url on the lists, they appear in the web interface.
/path/to/withlist -l -r fix_url xyz-sales -u www.domainofmine.net -v However, can anyone tell me why lists created in the web interface default to www.domainofmine.net but lists created from the command line default to localhost.localdomain? Of course, I can just run fix_url after every list creation in the shell script, but, is there a "template" somewhere that I can use to set it to use www.domainofmine.net for all lists? Hope someone can assist! Thanks in advance! Best Regards, Rick -->-->-->-->-->-->-->-->-->-->-->-->-->-->-->-->-->-->--> Rick Cogley (mailto:[EMAIL PROTECTED]) Tel: 03-5940-6880 || Fax: 03-5940-6881 || Cell: 090-4423-5475 (Outside Japan, remove leading zero -- +81-3-5940-6880) English: http://www.esolia.com || Japanese: http://www.esolia.co.jp Bilingual IT solutions and management firm -- eSolia. -->-->-->-->-->-->-->-->-->-->-->-->-->-->-->-->-->-->--> -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cogley, Rick Sent: Thursday, July 21, 2005 1:55 PM To: 'mailman-users@python.org' Subject: Re: [Mailman-Users] Mailman 2.1.5 - FQDN Question Apologies - it formatted wrong again, stringing the most relevant line together making it looked remarked out. Once more, it is probably obvious to you, this is the relevant line in the config: add_virtualhost('www.domainofmine.net', 'domainofmine.net') This is what works, as opposed to using the DEFAULT_URL_HOST etc above it. Thanks Rick -----Original Message----- From: Cogley, Rick Sent: Thursday, July 21, 2005 12:55 PM To: 'mailman-users@python.org' Cc: Cogley, Rick Subject: Mailman 2.1.5 - FQDN Question Hello, and Greetings from Japan - I'm new to the list and to Mailman, but I hope someone more experienced will be able to give me some pointers since I have not been able to get specific info from google or the manual on this problem. Please allow me to explain a little: After installing 2.1.5 from RPM on Fedora Core 4, I tried to set up mm_cfg.py with FQDN values, but was only able to get Mailman to start (service mailman start) if I only enter the virtual host section, like so, with all my other failed attempts remmed out with a #: =====8<========= ... # DEFAULT_URL_HOST = fqdn # DEFAULT_EMAIL_HOST = fqdn # DEFAULT_URL_HOST = www.domainofmine.net # DEFAULT_EMAIL_HOST = domainofmine.net # DEFAULT_URL_HOST = rcogley.user.myisp.com # DEFAULT_EMAIL_HOST = rcogley.user.myisp.com # Because we've overriden the virtual hosts above add_virtualhost # MUST be called after they have been defined. # NOTE: bug with quotes # add_virtualhost('DEFAULT_URL_HOST', 'DEFAULT_EMAIL_HOST') add_virtualhost('www.domainofmine.net', 'domainofmine.net') ... ========8<========= I was not able to get Mailman to start if I set DEFAULT_URL_HOST in the lines above the add_virtualhost line. It complains about not being able to find the hostname www. (I do have www defined in the DNS zone for domainofmine.net). Anyway, even with just the add_virtualhost line only, I am able to add lists from the web interface without trouble, and the lists that get created work correctly. It is when I try adding and configuring lists from the command line that I run into trouble. Here's the essence of the shell script I cobbled together from a couple of sources including the archives of this list. It's not sophisticated with for/do loops or anything but it seems to get the job done. I am using it to quickly create a few lists for a single company, and hope to increase efficiency in doing so. If we have the customer Acme, then this asks for the "short name" for the company at the prompt, and then proceeds to make 4 lists - acme-support@, acme-911@, acme-memo@, [EMAIL PROTECTED] ================8<================ #!/bin/sh # -- # mm-multi.sh - a script for creating Mailman lists. ... echo "mm-multi.sh - <\$Revision: 0.1 $>" # set global variables ... MMLISTLANG=en [EMAIL PROTECTED] ... echo echo Creating lists based on a structure... while [ "$x" != "y" ]; do echo echo Enter a short name for the client, no spaces, lowercase: read CSHORTNAME echo echo == SCRIPT PRESETS == echo Location of Mailman scripts: $MMBIN echo Location of Mailman aliases: $MMALIASES echo List language: $MMLISTLANG echo List Owner Email: $MMOWNEREMAIL echo List Admin Password: $MMADMINPASS echo echo == USER == echo Client Short Name: $CSHORTNAME echo echo "Is this correct? (y/n)" read x done ... /path/to/newlist -l en -q $CSHORTNAME-sales [EMAIL PROTECTED] s0m3pass /path/to/genaliases /path/to/add_members -r memberlistfile -w n -a y $CSHORTNAME-sales echo "description = '$CSHORTNAME-sales'" >/tmp/mm-multi-$CSHORTNAME-sales-tmp echo "available_languages = ['en', 'ja']" >>/tmp/mm-multi-$CSHORTNAME-sales-tmp echo "accept_these_nonmembers = ['[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.co\\\.jp$', '[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.net$', '[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.org$', '[EMAIL PROTECTED]@(.+\\\.|)domainofmine\\\.com$', '[EMAIL PROTECTED]@(.+\\\.|)gmail\\\.com$']" >>/tmp/mm-multi-$CSHORTNAME-sales-tmp /path/to/config_list -i /tmp/mm-multi-$CSHORTNAME-sales-tmp $CSHORTNAME-sales [[repeat newlist through config_list for three more "default" list names...]] echo Lists Just Created: echo /path/to/list_lists |grep $CSHORTNAME # cleanup rm -f /tmp/mm-multi* exit 0 ==============8<================ A couple of observations: * After I used this script to create a set of test lists, it sent mail to the owner (my account) FROM: [EMAIL PROTECTED] That indicates to me something is wrong with a config file somewhere. The web interface-created lists do NOT have this problem. They come in FROM: [EMAIL PROTECTED] * Although "Advertise this list when people ask what lists are on this machine?" is set to YES for these lists, all four that were autocreated by the script are all not visible in the web list at http://www.domainofmine.net/mailman/listinfo/. I can access them by typing in the expected URL in the browser address bar: http://www.domainofmine.net/mailman/admin/xyz-support/ * Even though I can bring up the admin area for the new lists by typing their URLs in manually (the links are not visible) the links all have localhost.localdomain in them, and so do not work. So my questions are: what do I set or focus on to make this localhost.localdomain anomaly go away? Also, those regexps in accept_these_nonmembers seem to overlap - does anyone know if there is a way to set the regexp so that all mail from any domain with a certain string is accepted? Any advice appreciated! THanks very much in advance... Sincerely, Rick Cogley Tokyo Japan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/rick.cogley%40esolia.co .jp Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/rick.cogley%40esolia.co .jp Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp