Status of virtual mailing list management
Hey folks,
I only just returned to mailman after a long time away and found 3.0 in active development. Yay!
Looking at the docs at http://packages.python.org/mailman/docs/README.html, I cannot find any mention of virtual hosting. Will mailman 3 be able to host foo@bar.com as well as foo@baz.org as two separate lists?
Thanks,
-- martin | http://madduck.net/ | http://two.sentenc.es/
"the truth is rarely pure and never simple. modern life would be very tedious if it were either, and modern literature a complete impossibility!" -- oscar wilde
spamtraps: madduck.bogus@madduck.net
On Wed, Feb 17, 2010 at 02:40:29PM +1300, martin f krafft wrote:
Looking at the docs at http://packages.python.org/mailman/docs/README.html, I cannot find any mention of virtual hosting. Will mailman 3 be able to host foo@bar.com as well as foo@baz.org as two separate lists?
Yes.
As for a reference, see, perhaps lines 282-294 of NEWS.txt:
http://bazaar.launchpad.net/~mailman-coders/mailman/3.0/annotate/head%3A/src...
282 Virtual domains are now fully supported in that mailing lists of the same
283 name can exist in more than one domain. This is accomplished by renaming
284 the lists/ and archives/ subdirectories after the list's posting address.
285 For example, data for list foo in example.com and list foo in example.org
286 will be stored in lists/foo@example.com and lists/foo@example.org.
287
288 For Postfix or manual MTA users, you will need to regenerate your mail
289 aliases. Use bin/genaliases.
290
291 VIRTUAL_HOST_OVERVIEW has been removed, effectively Mailman now operates
292 as if it were always enabled. If your site has more than one domain,
293 you must configure all domains by using add_domain() in your
294 etc/mailman.cfg flie (see below -- add_virtual() has been removed).
(along with posts, passim, in this list's archive).
Excitement :)
-- "what was asked of the Director in this case was not a statement of prosecuting policy but a proleptic grant of immunity from prosecution. That, I am quite satisfied, the Director had no power to give.” -- Bingham of Cornhill, R (Pretty) v DPP [2002] 1 AC 800
martin f krafft wrote:
I only just returned to mailman after a long time away and found 3.0 in active development. Yay!
Looking at the docs at http://packages.python.org/mailman/docs/README.html, I cannot find any mention of virtual hosting. Will mailman 3 be able to host foo@bar.com as well as foo@baz.org as two separate lists?
Yes. See "Wart removal" on the wiki page at http://wiki.list.org/x/vgAM.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
also sprach Mark Sapiro mark@msapiro.net [2010.02.17.1506 +1300]:
Yes. See "Wart removal" on the wiki page at http://wiki.list.org/x/vgAM.
Thanks.
I think it would be beneficial to add a note about Mailman 3 to the main page under "current version", including a link to the wiki page.
Ideally, there would also be a link from the launchpad project page.
Anyway, just suggestions that might prevent the next idiot like me from pestering the list. ;)
Thanks,
-- martin | http://madduck.net/ | http://two.sentenc.es/
"truth is stranger than fiction, but it is because fiction is obliged to stick to possibilities; truth isnt." -- mark twain
spamtraps: madduck.bogus@madduck.net
On Feb 16, 2010, at 8:40 PM, martin f krafft wrote:
I only just returned to mailman after a long time away and found 3.0 in active development. Yay!
Come join us over in mailman-developers! :)
Looking at the docs at http://packages.python.org/mailman/docs/README.html, I cannot find any mention of virtual hosting. Will mailman 3 be able to host foo@bar.com as well as foo@baz.org as two separate lists?
Yes. The key change is that lists are identified by their posting address (a.k.a. List-Post, a.k.a. fully-qualified list name), e.g. foo@bar.com and foo@baz.org. There's no place now where the list is identified internally as just 'foo'.
'bin/mailman create' is the command in MM3 to create new mailing lists. You have to configure Mailman to know about the domain before you can create a mailing list in that domain, but you can take a shortcut by adding the -d option to that command.
-Barry
also sprach Barry Warsaw barry@python.org [2010.02.18.1121 +1300]:
Looking at the docs at http://packages.python.org/mailman/docs/README.html, I cannot find any mention of virtual hosting. Will mailman 3 be able to host foo@bar.com as well as foo@baz.org as two separate lists?
Yes. The key change is that lists are identified by their posting address (a.k.a. List-Post, a.k.a. fully-qualified list name), e.g. foo@bar.com and foo@baz.org. There's no place now where the list is identified internally as just 'foo'.
I've had a hackish feature branch that did exactly this in place for years, actually. I am really glad to see this hit mainline.
In fact, I am so glad that I am considering setting up a new listserv just for test-driving mailman 3 with some real lists.
Thanks!
-- martin | http://madduck.net/ | http://two.sentenc.es/
this space intentionally left occupied.
spamtraps: madduck.bogus@madduck.net
participants (4)
-
Adam McGreggor -
Barry Warsaw -
Mark Sapiro -
martin f krafft