[Mailman-Developers] Results from 2.1a2's /mailman/create ... not as expected

[Barry A. Warsaw]

>>>>> "SB" == Scott Brown <scott-brown@home.com> writes:

    SB> I dont know if this was by design or not, but I went to my
    SB> (not externally accessible) test system at
    SB> http://www.testdomain.com/mailman/create and created a list
    SB> "justatest" and got the message tacked on the bottom of this
    SB> message.

    SB> Things that "JustDontLookRight" to me include:

    SB> - picked up the server's name, rather than the domain name of
    SB> the host it was triggered under.

    SB> Could it not be set up to take the virtual host underwhich it
    SB> was triggered (ie, testdomain.com), and use that as the
    SB> prefered name of the list?  The next page that comes up is
    SB> listed as being under that virtual host -- but all the links
    SB> point back to the machine's name.

See the latest cvs.  If you add add_virtualhost() calls to your
mm_cfg.py file, this should all now work.  I think this is what you
meant (in private email) about cheap-'n'-easy virtual hosts.  The
intent is to do everything we can to support virtual hosts in MM2.1,
short of eliminating the restriction of unique list names across the
entire site.  That I'm punting on until after MM2.1.

    SB> - Required me to use the sitepassword to create a new list...

    SB> How can I give that priveledge to someone else (like a virtual
    SB> host admin)...  I've not found any documentation anywhere that
    SB> describes how to register a valid user under a domain (such
    SB> that they can only create lists under that domain)

You should be able to set the "list creator's" password by using the
-c option to bin/mmsitepass.  This doesn't let you hand out unique
list creation privileges per virtual domain, but it does let you
delegate those privileges to folks who won't have site admin access.

    SB> - last line in message didnt have proper replacement of
    SB> "hostname".

    SB> Just a buglet - but I dont know enough python to fix it....

Should be fixed now.

    SB> - The email that is produced with the /etc/alias
    SB> additions... is it possible to define where that goes, say in
    SB> the mm_cfg.py?

    SB> It would be nice to be able to pipe those specific through
    SB> another email address that triggers a routine that could
    SB> actually do the append as root...

Currently it's hard coded to the "site owner" address, typically
mailman@your.dom.ain, where the LHS is defined by MAILMAN_SITE_LIST
and the RHS is defined by mappings in VIRTUAL_HOSTS (configured by
add_virtualhost() calls).  Don't change MAILMAN_SITE_LIST just to
change this behavior; for now hack Mailman/MTA/Manual.py to change the
destination address.

-Barry