Mark,
It has been suggested to me an approach that I thought might resolve the problem I am experiencing with the changes constantly made by OS X Server Admin application to Mailman's mm_cfg.py file. An it specialist who helped me review my OS X Server set-up and DNS settings suggested that I should change permissions on this file in order to prevent OS X Server from editing it. He tried changing the permissions on the file to rw-r--r-- but it still didn't work. From my limited knowledge of UNIX and terminal it appears to me that the ownership of the file belongs to -Mailman. Is this right ? Can either the permissions or the ownership (and perhaps both) on this file be modified so as to keep OS X Server from editing it ? Could these modifications have any adverse effect on Mailman's behavior or would the program work fine with this file as a read-only file ? What do you think ? According to the it specialist my set-up and DNS settings are fine. This is a relief. Now I know that the issue is very likely related to Apple's (poor) implementation of Mailman. I know one choice I have is to bypass this bundled version included with OS X Server and install a fresh version of Mailman. However, considering the work and time involved I would prefer, if possible, to work with the version I have and that is already set-up. What are your thoughts on this matter ? Thank you as always for your help, Joe On 12/12/10 10:22 PM, "Mark Sapiro" <m...@msapiro.net> wrote: > JRC Groups wrote: >> >> On 12/12/10 8:59 AM, "Mark Sapiro" <m...@msapiro.net> wrote: >> >>> I don't know. Please post the entire contents of your mm_cfg.py. The >>> above errors indicate that there is no add_virtualhost() for >>> www.domain.com, but this is not consistent with other things you >>> observe. >> >> Here it is: >> >> # Put YOUR site-specific settings below this line. >> MTA = 'Postfix' >> DEFAULT_EMAIL_HOST = 'dentserv.main.private' >> DEFAULT_URL_HOST = 'dentserv.main.private' > > > As you note below, the above entries are not what you want. > > >> VIRTUAL_HOSTS.clear() >> add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) >> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['3wforum.com'] > > > Is the '3wforum.com' domain what you refer to elsewhere as > 'domain.com'. If so, the above is probably fine (although the cat is > now out of the bag). If not, then it probably should be. > > >> VIRTUAL_HOST_OVERVIEW = Off >> >> As I copied the contents to paste them here I noticed that I had made a >> mistake. On the last entry I had "VIRTUAL_HOST_OVERVIEW - Off" instead of >> "VIRTUAL_HOST_OVERVIEW = Off". Once I corrected this entry I was able to >> have all lists displayed in the listinfo window. > > > Good. > > >> Now that I am able to view all lists displayed together in the same listinfo >> window I also noticed that the title to the listinfo page reads >> "dentserv.main.private Mailing Lists". In looking back at the mm_cfg.py file >> contents I noticed that something had been modified after I made the >> revisions you had suggested. The following entries were: >> >> DEFAULT_EMAIL_HOST = 'dentserv.main.private' >> DEFAULT_URL_HOST = 'dentserv.main.private' >> >> This is the name of my server and not the domain names as I had previously >> entered. So I proceeded to make the changes as you had previously suggested. >> >> DEFAULT_EMAIL_HOST = 'domain.com' >> DEFAULT_URL_HOST = 'www.domain.com' >> >> After these changes I was finally able to have the lists displayed in the >> listinfo window. I also noticed that the title above now reads >> "www.domain.com Mailing Lists". The titles is the same independent of >> whether I type "www.domain.com/mailman/listinfo" or >> "domain.com/mailman/listinfo". > > > Yes, this is a result of "VIRTUAL_HOST_OVERVIEW = Off" which in > addition to displaying all lists on the overview regardless of whether > the list's URL host matches the host in the URL accessing the page > also causes DEFAULT_URL_HOST to be treated as the host. > > >> After that I also made an attempt to create a new list from the web >> interface using "www.domain.com/mailman/create" and this time it worked fine >> without any error messages. >> >> I am left with a question: Why were the two lines above changed from the >> domain names I had entered following your suggestion to the name of the >> server ? Do you think it has something to do with my server settings or do >> you think it may be related with Apple's implementation of Mailman ? > > > I think it must have something to do with Apple's implementation of > Mailman. I suspect it has something to do with Apple's list creation > process. There is nothing in standard GNU Mailman that would edit > mm_cfg.py behind your back, nor would any non-Mailman process do this. > > Perhaps others on this list who are familiar with Apple Server could > shed more light on this. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
