FAQ
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 what I have.
BTW my server is a Redhat 6.1 Pro with SecureWeb 3.01

apples.com has mailing lists (which works fine). This domain is the "main
domain" (not a virtual domain)

The Root directory is
/www/apples.com/html

Now I have a virtual domain, oranges.com and this is in
/www/oranges.com/html

OK... The original mailman installed in /usr/share/mailman. The second
mailman went to /www/oranges.com/mailman. The idea is to setup all the
mailman (mailmen?) on the /www/virtual.domain.com/mailman


How Can I tell them apart on the httpd.conf??? Can you add several
Scriptalias as /mailman/ ???




How can I make one mailling list to go out (and come back) as appples.com
and oranges.com??

Do I work with virtual mailing users instead of aliases or do I use both?

Can you please help me? if not can you refer me to someone who can...


Thank in advanced!!!




__________________________________________
Sergio A. Murillo
sam at unah.hondunet.net

Search Discussions

  • Danny Yee at Mar 8, 2000 at 6:57 am

    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...
    You have to build Mailman multiple times, each time with a diferent
    --prefix= configuration. (Maybe /var/mailman/domain1.moredomain,
    /var/mailman/domain2.moredomain2, etc.). Don't forget to change
    Mailmam/mm_cfg.py appropriately in each installation! Of course you
    need an MTA with virtual domain support (I've got it working with qmail
    or postfix), to feed mail to each domain to the right scripts in each
    installation.

    This is really ugly if you've got a lot of domains, because not just
    the list information but also all the scripts have to be duplicated.

    Danny.
  • Chuck Dale at Mar 8, 2000 at 7:07 am

    Wrote Danny Yee on Wed, Mar 08, 2000 at 05:57:21PM +1100:
    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...
    You have to build Mailman multiple times, each time with a diferent
    --prefix= configuration. (Maybe /var/mailman/domain1.moredomain,
    /var/mailman/domain2.moredomain2, etc.). Don't forget to change
    Mailmam/mm_cfg.py appropriately in each installation! Of course you
    need an MTA with virtual domain support (I've got it working with qmail
    or postfix), to feed mail to each domain to the right scripts in each
    installation.

    This is really ugly if you've got a lot of domains, because not just
    the list information but also all the scripts have to be duplicated.
    Is anyone working on expanding the virtual domain support?

    Chuck
  • David Sexton at Mar 8, 2000 at 3:48 pm

    "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
    -------------- next part --------------
    --- MailList.py Sat Oct 30 02:11:48 1999
    +++ /home/sites/home/users/admin/MailList.py Thu Feb 3 08:55:24 2000
    @@ -117,7 +117,7 @@
    self.members[string.lower(addr)] = addr

    def GetAdminEmail(self):
    - return '%s-admin@%s' % (self._internal_name, self.host_name)
    + return '%s-admin@%s' % (string.lower(self.real_name), self.host_name)

    def GetMemberAdminEmail(self, member):
    """Usually the member addr, but modified for umbrella lists.
    @@ -159,15 +159,15 @@
    return None

    def GetRequestEmail(self):
    - return '%s-request@%s' % (self._internal_name, self.host_name)
    + return '%s-request@%s' % (string.lower(self.real_name), self.host_name)

    def GetListEmail(self):
    - return '%s@%s' % (self._internal_name, self.host_name)
    + return '%s@%s' % (string.lower(self.real_name), self.host_name)

    def GetListIdentifier(self):
    """Return the unique (RFC draft-chandhok-listid-02) identifier."""
    return ("%s <%s.%s>" %
    - (self.description, self._internal_name, self.host_name))
    + (self.description, string.lower(self.real_name), self.host_name))

    def GetRelativeScriptURL(self, script_name):
    prefix = '../' * Utils.GetNestingLevel()
  • Chuck Dale at Mar 26, 2000 at 4:25 am
    David,

    Thank you very much for these hints! I made the changes to MailList.py
    as you recommended. I was hoping for something like this.

    I have not experienced any problems yet.

    Could some Mailman top brass confirm whether making the changes that
    David suggested to MailList.py then changing the public name of the list
    will royally stuff something up that I've missed up till now?

    Thanks again
    Chuck

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedMar 8, '00 at 12:44a
activeMar 26, '00 at 4:25a
posts5
users4
websitelist.org

People

Translate

site design / logo © 2022 Grokbase