[Mailman-Users] mailman+exim+virtual domains

Wed Mar 6 08:30:08 CET 2002

I've found a few dialogues in the archives on this subject, but for
endmail  -- I've pasted them below, with links for each batch of
conversation....

(http://mail.python.org/pipermail/mailman-users/2001-November/015161.html)

On Monday 05 November 2001 03:08, V.S.Mony wrote:
> Hai,
>  I have installed mailman in my machine and is managing the mailing lists
> for one domain. It has multiple domains hosted on it. Can one single
> installation of mailman be used to manage mailing lists for multiple
> domains?
>
> Thanks in advance
>
> Venkat

Yes.  It's a touch more complicated, but easily doable.  You have to setup
the virtual domains under your MTA (mailserver) and in your Webserver, then
simply set Mailman to use those virtual addresses, under General Options in
the Admin interface.

Jon Carnes

--------------Follow-up---------------------

On Wednesday 07 November 2001 00:22, V.S.Mony wrote:
> There is only a field with the description  'Hostname the list prefers'
>
> Can we give multiple domains in that field?
> i mean abc.com,xyz.com in the same textbox?
>
> Then will it recognise mails to both abc.com and xyz.com
>
> Venkat

Negative.  You put "abc.com" in for the domain it prefers.  If the list is
called mylist at abc.com, then you create an alias for it called mylist at xyz.com

The last step is to identify "mylist at xyz.com" as a list that is treated as
though it were "mylist at abc.com" by Mailman.  You do that by web-ing over to
the admin page and on the Privacy Options page, putting the address into
the field:
   Alias names (regexps) which qualify as explicit to
   or cc destination names for this list. (Details)

Works just fine there after - Jon

---------------Separate Dialogue-------------------
I didn't follow this conversation, which seems to conclude it was a sendmail
problem:

1. Bill Moseley asks question, seems quite relevant to me:
***************
I have my lists all setup to use the full name of the host.

  DEFAULT_HOST_NAME   = 'mardy.hank.org'

This is the same host as simply hank.org.  I just tried to subscribe to a
list, and the confirm mail came like this:

  Reply-To: test-request at hank.org

The list settings have not changes (they still say mardy.hank.org).

The problem is I have all mail to @hank.org to one address in sendmail's
virtusertable, so it needs to go to mardy.hank.org to not get bypassed by
my virtusertable entry.

So, the question is, why did mailman set the reply to to simply @hank.org
instead of @mardy.hank.org?  What settings should I look at?

Bill Moseley
mailto:moseley at hank.org
****************
2. Jon Carnes answers:
****************
So you changed it in your ~mailman/Mailman/mm_cfg.py file but did you go
into the web-admin and change it on the General Options page for the lists
that already exist?
   Host name this list prefers:  mardy.hank.org

Jon Carnes
****************
3. Bill Mosely responds:
****************
At 05:59 PM 11/28/01 -0500, Jon Carnes wrote:
>So you changed it in your ~mailman/Mailman/mm_cfg.py file but did you go
>into the web-admin and change it on the General Options page for the lists
>that already exist?
>   Host name this list prefers:  mardy.hank.org

Nope, that's what I meant when I said:

> The list settings have not changes (they still say mardy.hank.org).

Should have been

The list's settings have not changes (they still say mardy.hank.org).

I assume the settings are in the .db file for each list:

> strings config.db | grep hank.org
http://hank.org/mailman/s
moseley at hank.orgi
moseley at hank.orgs
moseley at hank.orgi
mardy.hank.org0

Hum.
*****************
4. Then Bill seems to say he's found the answer:
*****************
.... Wait, could it be sendmail is changing those headers?

250 mardy.hank.org Hello localhost [127.0.0.1], pleased to meet you
mail from: b at hank.org
250 2.1.0 b at hank.org... Sender ok
rcpt to: moseley at hank.org
250 2.1.5 moseley at hank.org... Recipient ok
data
354 Enter mail, end with "." on a line by itself
To: moseley at hank.org
From: xxx at mardy.hank.org
Errors-to: yyy at mardy.hank.orgSubject: well?bye.
250 2.0.0 fASNBQu12953 Message accepted for deliveryquit----- mail ----
Date: Wed, 28 Nov 2001 15:11:33 -0800To: moseley at hank.org
From: xxx at hank.org
Errors-to: yyy at hank.org
Subject: well?

bye

Damn.  Never mind.  Now, if I could only remember how to disable that....
******************

And that was the entire dialogue... at:
http://mail.python.org/pipermail/mailman-users/2001-November/015752.html

---------------------Finally, some more!!!!---------------------------
At http://mail.python.org/pipermail/mailman-users/2001-November/015637.html

Bill Moseley getting help from others now:

Bill Moseley wrote:

> Do people use shell scripts to do all this work?

    Nope, by hand.

> su - mailman
> bin/newlist foo
> su
> <edit /etc/mail/aliases>
> newaliase
> <edit /etc/mail/virtusertable>
> makemap hash virtusertable < virtusertable
> <restart sendmail>
>
> Actually, the problem with that is the bin/newlist should be done last as
> it sends mail to the new list admin, and if done first, the list isn't
> really setup yet.

    I open two windows to my server:

    window 1 [ as mailman ]:
        ./bin/newlist
            - list name
            - email
            - password
            [ pause - go to window 2 ]

    window 2 [ as root ]:
        vi /etc/mail/aliases
            add list aliases
        vi /etc/mail/virtusertable
            add list users
        makemap on virtusertable
        newaliases
            [ back to window 1 ]

    window 1 [ as mailman ]:
        hit return
            MM sends out email.

At 12:12 PM 11/26/01 -0700, Ashley M. Kirchner wrote:
>    In your virtusertable:
>
>    #mailing lists
>    test at hank.org          test
>    test-admin at hank.org    test-admin
>    test-request at hank.org  test-request
>    test-owner at hank.org    test-owner
>
>    #catchall rule
>    @hank.org              moseley+%1

Thanks, that's what was I worried about.  ;)

Do people use shell scripts to do all this work?

su - mailman
bin/newlist foo
su
<edit /etc/mail/aliases>
newaliase
<edit /etc/mail/virtusertable>
makemap hash virtusertable < virtusertable
<restart sendmail>

Actually, the problem with that is the bin/newlist should be done last as
it sends mail to the new list admin, and if done first, the list isn't
really setup yet.

Thanks for the help!

Bill Moseley
mailto:moseley at hank.org