On Tue, Apr 26, 2005 at 07:50:21AM +0200, Mathieu Roy wrote: > > 1) I use the e-mail from the account instead of [EMAIL PROTECTED] (since > > Savannah doesn't forwards [EMAIL PROTECTED]),< > > Hum. It is best not to disregard real user address but > indeed it means forwarding must be activated. > But wouldnt it be easy for you to have the aliases on the > mailing-server server: that would make the stuff working but it would > not implies that it would be working from the outside. That may be an > acceptable in-between solution.
What are the advantages of not using the user's real mail? For me, in particular, it will certainly not be easier, but don't care for me :) > > 2) I add @lists.[non]gnu.org at the end of the list name when calling > > 'newlist' (uses the associated virtual domain configuration). Beware, > > I actually use again 'mailing_list_host', which is currently > > deprecated, but fits my needs. > > So this cannot and should not be included, as it use deprecated stuff. > > The way mailing-list address must be defined is using Mailing-list > address (ex: [EMAIL PROTECTED]). That's not the way Mailman allows you to create lists on virtual domain. It wants your virtual HTTP host and get the associated mail domain - not the opposite. Check newlist --help. If you want it is possible to create another field, but it appears that this field contains exactly the HTTP virtual host Mailman wants. > > and 3) added a bunch of TODOs comments. > > > > Also, the script won't work anyway without a wrapper around 'newlist'; > > actually there is no official, standard way to handle multiple > > domains. lists.gnu.org uses a way, some installations (including what > > is recommended in the Mailman Debian package documentation) use > > something a bit different (I think Savannah's way is better since it > > allows easy aliasing among domains). > > > > The wrapper's role is to do a few things afest newlist is called (tell > > Exim what domain the list uses, > > That could be done by sv_mailman just the way it preconfigure the list > (private etc...), no? Why not, but as I said this assumes a particular way to expose the virtual domains, which the user may not agree with. I think it's best not to do it in sv_mailman. When Mailman will offer a standard way to publish virtual domains to the MTA, then we'll be able to work on it. Configuring the list virtual domain is still useful. > > fix a bug in newly created list with our version of Mailman, export > > the updated list of mailing lists to another mail system). > > That part could not be part of Savane, it is specific to Savannah's > arrangements. I didn't intend to :) [incidentally I don't think the bugfix is not Savannah-specific] -- Sylvain
