Matt England wrote: > >I think I get the high-level concept here, but I'm fuzzy on some things, >including how to implement this. > >Is this how one can/should it? In this context: > > Default URL and email host domain = lists.default.tld > Virtual URL and email host domain = lists.virtual.tld > Setup [EMAIL PROTECTED] as usual
Yes. This is what you do. You could just stop here, but there is a small problem. Assume for discussion that the web hosts for these domains are www.default.tld and www.virtual.tld, etc. The problem is that the page at http:/www.virtual.tld/mailman/listinfo will say If you are having trouble using the lists, please contact [EMAIL PROTECTED] and likewise the page at http:/www.virtual.tld/mailman/admin will say (Send questions and comments to [EMAIL PROTECTED]) Now your choices are: 1) Ignore this (not a good idea if mail to those addresses doesn't work) 2) Change get_site_email in Mailman/Utils.py to always use DEFAULT_EMAIL_HOST 3) Make the above address(es) work. >...how would I route and web-interface [EMAIL PROTECTED] to >[EMAIL PROTECTED] (assuming this what I should do)? I'm not yet >sure exactly how to email alias/route this (although I suspect I can >probably do this via my qmail or postfix setup), but I really have little >idea about how to make the user/admin web interface correlate these 2 things. This question relates to choice 3. I don't know the answer in your specific case. It may be that you don't have to do anything. If your mail aliases are global so that for example, an alias like mailman: "|/var/mailman/mail/mailman post mailman" (or whatever your equivalent is) applies to all mail to [EMAIL PROTECTED] regardless of what * is, then you are done. OTOH if aliases are per virtual domain, then you need an alias like the above (and maybe the other mailman-* ones too) for each domain. The 'pipe' part of the alias is the same in all cases except for the 'post' part which differs for the mailman-* addresses. What you have to ensure is that all mail for the 'mailman' address regardless of domain gets piped to '/var/mailman/mail/mailman post mailman' (or whatever the correct path is) and similarly for the other mailman-* addresses. I note from another post that you are using qmail-to-mailman.py. I don't know what that does, but you'll have to translate the above into that environment. >I will also have multiple virtual domains (call them lists.virtual2.tld, etc). This shouldn't be a problem. -- 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
