Tom Ray wrote: > >Thanks for the reply and sorry if I wasn't overly clear. Each domain was >setup as --prefix=/home/sites/domainname.com/mailman
This should be fine, but in the OP you said that the 2.1.6 web pages identify themselves as 2.1.7 which they shouldn't at all be doing if they are completely separate. Also, if they identify themselves as 2.1.7, they are probably getting Defaults.py/mm_cfg.py from one of the 2.1.7 domains too. Note that the value of $prefix is compiled into the cgi-bin wrappers, so each set must be configured for it's own domain. >Each site has it's own cgi-bin but I did setup everything as >mailman:mailman for user:group. That shouldn't be a problem. >I'll see what I can do about upgrading >the 2.1.6 lists to 2.1.7 and see if that has any effect. It shouldn't (unless you mean the while configure/make upgrade), but fix_url as mentioned in FAQ 4.29 might. >> Were the 2.1.6 lists created in their current domains? If not >> see ><http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.029.htp>. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ 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
