[Mailman-Users] Per Virtual domain customizations

[John Locke]

On Tue, 2003-02-04 at 00:40, Simon White wrote:
> 03-Feb-03 at 20:00, John Locke (mail at freelock.com) wrote :
> > 
> > 1. Is there any support for storing member information in a SQL
> > database, with MM 2.1?
> > 
> 
> I do this via synchronisation. A script that calls
> add_member/remove_member called from the code that does the
> INSERT/DELETE query in SQL. It's not particularly robust but it works.
> 
Yes, this is what I was thinking I would have to do. I had just found
some references to a SQL "member adapter" for Mailman, during a web
search, but was unable to find anything about implementing it.

The biggest issue is that my web server is separate from my mail server
(both are running MySQL, but for reliability, I'm having the web site
hosted). So I'm gonna have to develop some sort of replication
/synchronization scheme to handle connection outages...


> > 2. Is there any way to customize lists on a per-virtual-domain basis?
> > Something as simple as having a different mm_cfg.py, and a different
> > templates/ directory for each domain would be what I'm looking for--but
> > can't quite get it to work. 
> 
> I don't know if this is fully possible, but I know each list can have
> it's own language preference so I guess there are other parameters each
> list can have uniquely.

So far I've been able to set per-list configurations, using config_list
after the list is created. I found if I create an "en/" directory inside
the directory for the list, any templates I put in there are used before
the ones in the main template directory. But this doesn't help for the
initial list-creation email sent to the list admin (because the list
isn't created beforehand), or for the ADMIN_CATEGORIES variable (because
it seems to be site-wide).

Any other ideas?

Thanks,
-- 
John Locke
http://freelock.com
Just launched: http://teamcheckin.com