[Mailman-Users] virtual domains problem

[Mark Sapiro]

Sean Roe wrote:

>Unfortunately, I have to do it this way, with multiple instances, as one 
>group of lists are using the mysql adapter and one group isn't.  


If you use the extend.py mechanism to specify the MysqlMemberships.py
MemberAdaptor rather than patching MailList.py, you can use
MysqlMemberships.py for only a subset of lists. It is not quite
automatic as you would have to manually copy an extend.py file to the
lists/listname/ directory following creation of a list that would use
MysqlMemberships.py, but it can be done.
 

>Getting 
>back to the original posting, do you know why I am picking up that colon 
>on the beguining of the domainname?


It is not clear to me from the prior posts in this thread exactly what
you've tried. You said in a prior post -

The changes I made were to exim's list_macrodefs:
from:
MM_LISTCHK=MM_HOME/lists/${lc::$local_part}/config.pck
to:
MM_LISTCHK=MM_HOME/lists/${lc:$local_part}/config.pck

and mailman_router:
from:
require_files = MM_LISTCHK
to:
require_files = <; MM_LISTCHK

but it is not clear if you also changed MM_HOME. There is possibly
confusion over whether or not a doubled colon is required in MM_HOME
for

MM_LISTCHK=MM_HOME/lists/${lc::$local_part}/config.pck

but the several other places where MM_HOME is used definitely do not
want the colon to be doubled.

Thus it seems to me you want

MM_HOME=/data/mailman/${lc:$domain}

and

MM_LISTCHK=MM_HOME/lists/${lc:$local_part}/config.pck

and to be sure you don't need doubled colons in MM_LISTCHK,

require_files = <; MM_LISTCHK


-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan