[Mailman-Users] Virtual Domains, Patch, Question

[Ace Suares]

Hi,

This is in reply to a message of David Sexton
which appeared Wed, 08 Mar 2000 15:48:07 +0000 
on this list.

He describes a patch to MailList.py that should make virtual user support 
more easy.
I applied the patch to 2.0beta5-1 and the patch seemed to work. (I mean, the 
file was patched without rejections).


However, I can not change "The public name of this list (make case-changes 
only)." in the admin screen. The cgi-bin program says that it won't allow 
anything else then case changes.

How to solve this ? The admin program in cgi-bin is not a script, and the 
config.db per list is a database, so i can not meddle around with it directly.

What is the proper way to set up virtual domains ? I understand mailman has 
support for it, but if no list can have the same name in different domains, 
it's not very usefull. 

In the archives I didn't find many usefull answers; this patch of Dave Sexton 
seems the closest thing to a solution...

If anyone has info about this issue, would be greatly appreciated !

_Ace Suares
 
Follwing the original message:


"Sergio A. Murillo" wrote:
> 
> I've been trying to configure Mailman to work with a virtual domain on a web
> server with serveral virtual domains. I read  William R. Dickson sugestion
> of installing a copy of mailman for each of the virtual domains.
> How do i do this?/?? I've been traying all week now and still no luck...

        This is the way I have it done (I'm not 100% certain of the
security/reliability of this but it has worked so far):

        I have one user set-up purely for mailman and mailman is
installed in
that user's directory & web space. All the administration for the lists
are done through this one URL (although it may be possible to put
wrappers around this).

        Onto the 'meat'...

        I'm assuming that you have set up the mail aliases and virtual
user
table in the following manner:-

        virtusertable:

        <list-name>@<domain>            list-<list-name>
        <list-name>-admin@<domain>      list-<list-name>-admin
        <list-name>-request@<domain>    list-<list-name>-request
        <list-name>-owner@<domain>      list-<list-name>-admin

        aliases:

        list-<list-name>:               "|wrapper post <list-name>"
        list-<list-name>-admin:         "|wrapper mailowner <list-name>"
        list-<list-name>-request:       "|wrapper mailcmd <list-name>"

        To change the domain of the list, you would go into the admin
screen
and change the host name of the list. This will allow you to
successfully set-up & use list1 at domain1.com & list2 at domain2.com.

        Is this perfect? No.

        This would work until you needed two lists of the same 'name'
eg:
                announce at domain1.com and announce at domain2.com

        A workaround for this is to embed the domain name into the list
name
and create lists like the following:-
                domain1-com-announce  & domain2-com-announce

        This now looks really clunky as the list would be at
domain1-com-announce at domain1.com etc.

        But .. if you mangle the entries in virtusertable, incoming mail
works
....

        virtusertable
        announce at domain1.com            list-domain1-com-announce
        announce at domain2.com            list-domain2-com-announce
                .. do a similar thing for the request & admin etc.
addresses.

        aliases
        list-domain1-com-announce:      "|wrapper post
domain1-com-announce"
        list-domain2-com-announce:      "|wrapper post
domain2-com-announce"
                <etc. etc>

        Now we're *almost* there. The addresses that mailman puts into
messages
it sends out will contain the full list name
(domain2-com-announce at domain2) , not the short version you want. Back in
the mailman admin screens, there is a field that in the public name of a
list. It seems to indicate that mailman will use this name when
generating addresses but changing this only does half the job.

        I've hacked around a bit with MailList.py and got much better
reults.
If you apply the attached patch and change the 'public name' for the
lists, it should work.

        ** NOTE ** I have very little experience of Python (I'm a perler
at
heart) and almost no appreciation of the structure of Mailman so I
cannot guarrantee that these changes will not foul everything up. The
docs say that you should not change the public name of a list and,
although it is working so far, I am not totally sure of the implications
of this.

        Hope this helps,

        Dave

-- 
David Sexton

Network Technician
Sapphire Technologies Ltd.
Tel: +44 (0) 1642 702100
Fax: +44 (0) 1642 702119

-----------------------------------------------
Any opinions expressed in this message are those of the individual and not 
necessarily the company.  This message and any files transmitted with it are 
confidential and solely for the use of the intended recipient.  If you are 
not the intended recipient or the person responsible for delivering to the 
intended recipient, be advised that you have received this message in error 
and that any use is strictly prohibited.

Sapphire Technologies Ltd
http://www.sapphire.net


<patch not duplicated here>




| Ace Suares, Internet Consultancy and Training
| Keizersgracht 132, 1015 CW AMSTERDAM, NL
| phone: 06 557 06 554    (+31 6 557 06 554)
| fax: 020 870 770 5      (+31 20 870 770 5)
| mailto:ace at suares.com PGP Key idea: 0x39B81FE5
| http://www.suares.com