
- You have the list owner change their DNS to point to you
- You host their website and their domain
- You provide a mechanism for them to update their web pages
- You provide a mechanism for them to access their e-mail
- You become a general support/ISP for said domain, even though you only agreed to host a list for them.
Nono. You set up mailman.theirdomain.com or lists.theirdomain.com and point *it* at your server. You don't host anything but lists, all the lists then have addresses that are mylist@lists.theirdomain.com and if they want to alias mylist@theirdomain.com, then that's their job and none of your business.
Now, I can totally see how you could wind up getting stuck hosting other stuff once you did this ("We want there to a page on http://mailman.theirdomain.com/ instead of just /mailman/listinfo", "we want the list to give mylist@theirdomain.com on the listinfo pages", etc.) But to be fair, there is no need for you do handle anything other than a subdomain which need not be used for anything but lists.
But anyhow, you seem to have a good idea of what you'd like, and you've clearly got the ability to make the patch if you're handling this stuff right now. Would you be willing to write it? All it takes now is a patch that's good enough for commiting, and you should be able to have what you want.
Terri