Tom Browder wrote:
>Question 1:
>=========
>
>Current situation:
>------------------------
>
>I have now pretty much a working solution for this situation (postfix
>and mailman installed with Ubuntu packages on 64-bit 10.04 LTS (Lucid
>Lynx) :
>
> 1 server
> 1 "real" domain: realdomain.com
> 2 virtual domains: virtual-1.org
> virtual-2.org
>
>All are accessed successfully through SSL/TLS (https).
>
>Desired situation:
>------------------------
>
>I can get new lists at the virtual domains okay, but here's what I
>would like to do: change the mailing list virtual domains to:
>
> 2 virtual domains: lists.virtual-1.org # this is my default domain for
> mailman
> lists.virtual-2.org
>
>BUT present the lists to the users as, say, i...@virtual-1.org
Every list has two attributes, a web_page_url with a host name of the
web domain and a host_name which is the name of the email domain. so,
yes, you can do what you want.
In mm_cfg.py you want
DEFAULT_URL_HOST = 'lists.virtual-1.org'
DEFAULT_EMAIL_HOST = 'virtual-1.org'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('lists.virtual-2.org', 'virtual-2.org')
and only if you are using Mailman/Postfix integration
MTA = 'Postfix'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virtual-1.org', 'virtual-2.org']
If you are using postfix_to_mailman.py, you want
MTA = None
and you want both virtual-1.org and virtual-2.org mapped to the mailman
transport in transport_maps, but this won't work if you have real
users with addresses @virtual-1.org or @virtual-2.org
See the FAQ at <http://wiki.list.org/x/lYA9> for more info.
After making those mm_cfg.py changes, run fix_url as follows
For lists in the virtual-1.org domain (DEFAULT_*_HOST), run
bin/withlist -l -r fix_url LISTNAME
For lists in the virtual-2.org domain, run
bin/withlist -l -r fix_url LISTNAME -u lists.virtual-2.org
Following that, if you are using Mailman/Postfix integration, run
bin/genaliases
to rebuild data/mailman* and data/virtual-mailman*.
>I had some mixed success early on, but other problems intervened. Now
>that the other problems have been solved, I want to blow everything
>away and start over but only if the "Desired situation" is feasible:
>
>Question 2:
>=========
>
>Can I also do this on the real domain:
>
>Create a new subdomain and mailing lists:
>
> lists.realdomain.com <= let postfix and mailman handle this as a
>virtual domain
>
>And also as desired for "Question 1,"
>
> BUT present the lists to the users as, say, n...@realdomain.com
Just add another
add_virtualhost('lists.realdomain.com', 'realdomain.com')
in mm_cfg.py and treat this like the others, except if realdomain.com
is local in Postfix and has real users, you can't use
postfix_to_mailman.py[1], and you don't add 'realdomain.com' to the
POSTFIX_STYLE_VIRTUAL_DOMAINS list.
[1] You really can still use postfix_to_mailman.py, but you can't
simply put "realdomain.com: mailman" in your transport_maps table. You
have to do things like
somel...@realdomain.com: mailman
somelist-boun...@realdomain.com: mailman
somelist-conf...@realdomain.com: mailman
(etc)
for all 10 addresses for each realdomain.com list at which point, you
are much better off using regular Mailman/Postfix integration.
--
Mark Sapiro <m...@msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
