On Sun, 8 Jul 2007, Barry Warsaw wrote: > On Jul 7, 2007, at 4:23 PM, Krystal F. Zipfel wrote: > > > Is there any consideration made, or is it possible to have Mailman > > recognize that "[EMAIL PROTECTED]" is different than > > "[EMAIL PROTECTED]", and operate as normal based on that? > > I don't expect 2.2 to be any different than 2.1 in this regard, > however this is already fixed in the Mailman 3 dev branch.
I would like to register a "+1" towards at least the beginnings of proper, multiple-domain support. No need at all for this to be the whole thing, but at least its basic foundations. Even just a hidden "own-risk" installation option of having the listnames (and references to them) internally stored and processed as "[EMAIL PROTECTED]" would help. What worries me about the "fixed in the Mailman 3 dev branch" is the timescale. You mention both that "2.1 is (shockingly) 4.5 years old", and that there is "no ETA for Mailman 3.0". So with such a basic, minimal foundation (for true multiple domains) in place, then those of us who would really like it a.s.a.p. in our service environments (i.e. not Mailman 3) would be able to contribute to building it, perhaps as a subproject (analogous to those you mention for "SQAlchemy/Elixir", archiver, "web u/i", etc.). Anyway, thanks for your work over the years,and now on Mailman. It is much appreciated! -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : UNIX Team Leader Durham University : : South Road : : http://www.dur.ac.uk/t.d.lee/ Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. : ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
