The mailing list for listmasters using Sympa

[Michael Howe <address@concealed>]

On 20/05/14 22:43, Steve Shipway wrote:
>> I'm trying to work out how to let list owners stop sympa archiving
> messages
>> for their lists - that is, not saving them at all (not just saving them
> and making
>> them inaccessible).
> 
> Why not just set archive.max_month for the archive to 0?  Of course this
> will also delete all existing archives for that list.

A good idea - sadly, there's a test:
 if ($list->{'admin'}{'web_archive'}{'max_month'}){
which fails unless max_month is a true value (and 0 doesn't count).

However, that set me on the right track, and it turns out that if you
can remove the web_archive.access parameter archiving doesn't happen.
This is easy enough to do with edit_list_request.tt2 by adding in an
extra option (with apologies for the wrapping my mail client has applied):

Index: sympa/web_tt2/edit_list_request.tt2
===================================================================
--- sympa/web_tt2/edit_list_request.tt2 (revision 43969)
+++ sympa/web_tt2/edit_list_request.tt2 (revision 43970)
@@ -280,6 +281,13 @@

                                       [% IF key.type == 'scenario' %]
                                         <!-- Scenario -->
+                                        [% IF p.name == 'web_archive'
AND key.name == 'access';
+                                        SET empty_string = '';
+                                        key.value.${empty_string} = {
+                                          'name' => '',
+                                          web_title => 'disable archiving'
+                                        };
+                                          END %]
                                         [% IF key.may_edit == 'write' %]
                                           <select name="single_param.[%
p.name %].[% key.name %].name" id="single_param.[% p.name %].[% key.name
%].name">
                                             [% FOREACH scenario =
key.value %]


Michael

-- 
Michael Howe, Systems Development and Support Section
IT Services, University of Oxford