Mailman 2.1.2, Postfix 2.0.13, virtual domains
Hi all,
I have set up the above on a FreeBSD 4.7 system with the intention of being able to host per-virtual-domain mailing lists.
I want to be able to have:
list01@domain1.com and list01@domain2.com
as completely separate, autonomous lists.
First, is this even possible using stock Mailman?
And if so, I've been having trouble attempting to set it up. Despite adding virtual domains to the POSTFIX_STYLE_VIRTUAL_DOMAINS variable in mm_cfg.py, as well as trying to add "add_virtualhost('mail.domain2.com') invocations to mm_cfg.py, Mailman _always_ tries to create lists in the default domain.
Example:
$ bin/newlist virt4@default-domain.com ... (list created)
data/virtual-mailman:
virt4@default-domain.com virt4 virt4-admin@default-domain.com virt4-admin ...
$ bin/newlist virt4@domain2.com ... List already exists: virt4
Or, if I create the virtual one first, it creates the list in the default domain anyway.
Am I doing something wrong, or is this impossible? If it cannot be done with Mailman, is there some other MLM I should be looking at?
Thanks.
Jim Breton said:
I have set up the above on a FreeBSD 4.7 system with the intention of being able to host per-virtual-domain mailing lists.
Yay! Another FBSD user! :)
I want to be able to have:
list01@domain1.com and list01@domain2.com
as completely separate, autonomous lists.
Can't do it :( It'd have to be:
list01@domain1.com list02@domain2.com
If Mailman had a little more (no offense, I just can't think of a better term to use) intelligence in it, when you set up for virtual domains it'd do things like create a directorynamespace like /usr/local/mailman/lists/domain2.com/, etc. so you *could* put lists with the same name in different domains...
And if so, I've been having trouble attempting to set it up. Despite adding virtual domains to the POSTFIX_STYLE_VIRTUAL_DOMAINS variable in mm_cfg.py, as well as trying to add "add_virtualhost('mail.domain2.com') invocations to mm_cfg.py, Mailman _always_ tries to create lists in the default domain.
Example:
$ bin/newlist virt4@default-domain.com ... (list created)
data/virtual-mailman:
virt4@default-domain.com virt4 virt4-admin@default-domain.com virt4-admin ...
$ bin/newlist virt4@domain2.com ... List already exists: virt4
This happens because of the prior explanation...
Hope this helps...
Glenn
The original portions of this message are the copyright of the author (c)1998-2002 Glenn E. Sieb. ICQ UIN: 300395 IRC Nick: Rainbear "All acts of Love and Pleasure are Her rituals"-Charge of the Goddess
On Thu, 2003-07-31 at 13:42, Glenn Sieb wrote:
Jim Breton said:
I have set up the above on a FreeBSD 4.7 system with the intention of being able to host per-virtual-domain mailing lists.
Yay! Another FBSD user! :)
I want to be able to have:
list01@domain1.com and list01@domain2.com
as completely separate, autonomous lists.
Can't do it :( It'd have to be:
list01@domain1.com list02@domain2.com
If Mailman had a little more (no offense, I just can't think of a better term to use) intelligence in it, when you set up for virtual domains it'd do things like create a directorynamespace like /usr/local/mailman/lists/domain2.com/, etc. so you *could* put lists with the same name in different domains...
Well, technically, you could have two or more parallel installs of Mailman. There are quite a few folks who do that when they have just a few virtual domains to worry about.
Also, you can alias list01@domain2.com ==> list01-domain2 And let the (hidden) real name of the list be list01-domain2. Of course then you have to do a lot of editing of the web-pages to display the domain information that you want.
That is the way I normally do it. The webpages all aliases properly as do the email addresses, so the end-user is non the wiser.
And yes, it sure would be easier if mailman used only the virtual host information when setting up it's web pages and sending out its emails.
Good Luck
This, along with per-domain create passwords are by far at the top of my feature wish-list. Aliasing is a royal PITA because it is a completely manual process which gets completely out of hand when you are hosting many domains/lists on one machine.
On Thursday 31 July 2003 11:42 am, Glenn Sieb wrote:
If Mailman had a little more (no offense, I just can't think of a better term to use) intelligence in it, when you set up for virtual domains it'd do things like create a directorynamespace like /usr/local/mailman/lists/domain2.com/, etc. so you *could* put lists with the same name in different domains...
-- Richard B. Pyne rpyne@kinfolk.org
participants (4)
-
Glenn Sieb -
Jim Breton -
Jon Carnes -
Richard Pyne