The mailing list for listmasters using Sympa

[Mike Carter <address@concealed>]

Hello All;

We are in the process of migrating from a legacy lists system to Sympa 
6.1.22.  One of our requirements is that we would like to turn off Sympa list 
archiving entirely for all lists including those we migrate and new lists 
going forward.  

So, the question is, is the best way to do this to do what David suggests for 
Peter's question?  I've seen a couple of threads dating back to 2011 that 
talk about a "web_archive_feature" binary parameter but it doesn't seem to 
have been implemented?  

Thanks in advance!

Mike Carter
Enterprise Services
Office of Information Technology
University of Colorado Boulder 

On Fri, Jun 27, 2014 at 05:19:35AM -0600, David Verdin wrote:
> Hi Peter,
> 
> What you have in mind is completely exact.
> 
> You can define a single config.tt2 file where all the parameter
> values will be replaced by data found in the XML file.
> 
> The definition of what you can find in a config file is available in
> the following link. It is the list of parameters you can use in a
> config file:
> 
> https://www.sympa.org/manual/list-parameters#list_configuration_parameters
> 
> Regards,
> 
> David
> 
> Le 27/06/14 13:07, Peter Grandi a écrit :
> >Will be moving a few thousand lists to Sympa, and they have been
> >created on the original system with somewhat weird combinations
> >of permissions.
> >
> >We will have a given set of default list types and related
> >profile '.tt2' templates for newly created lists, but for the
> >lists above I'd like to create configurations as close as
> >possible to the original ones, weirdness and all.
> >
> >This would require probably creating dozens of subtly different
> >list profile '.tt2' templates, and I'd rather avoid that.
> >
> >Looking at the way 'sympa.pl --create_list --input_file ....'
> >works the XML file is described here:
> >
> >   http://www.sympa.org/manual_6.1/list-creation#xml_file_format
> >
> >and my understanding is that 'list', 'type' and 'description'
> >are mandatory elements and must have those names, but all the
> >others are just fed into Template Toolkit for the expansion of
> >the 'config.tt2' file for the given 'type'.
> >
> >If that were the case I could create a single 'config.tt2' file
> >with a larger set of template parameters and handle all the
> >variety in parameters by setting values in the input XML file
> >instead of creating many mlist types with hardcoded fields.
> >
> >Is that something I can do?
> >
> >The consequent question is then where is the list of possible
> >options recognized by 'sympa.pl' in the file _generated_ from
> >the XML input file and the 'config.tt2' file; I have had a look
> >at several sample list profile 'config.tt2' files and I think
> >that I have some idea, but a pointer to a full list would be
> >welcome.
> 
> -- 
> A bug in Sympa? Quick! To the bug tracker!
> <https://sourcesup.renater.fr/tracker/?group_id=23>
> RENATER logo
> *David Verdin*
> Études et projets applicatifs
> 
> Tél : +33 2 23 23 69 71
> Fax : +33 2 23 23 71 21
> 
> www.renater.fr <http;//www.renater.fr>
>       RENATER
> 263 Avenue du Gal Leclerc
> 35042 Rennes Cedex
> 
> 
> 



-- 

                                - Mike