Skip to Content.
Sympa Menu

en - Re: [sympa-users] Customising subscription confirmation requests and other questions

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Chris Hastie <address@concealed>
  • To: address@concealed
  • Subject: Re: [sympa-users] Customising subscription confirmation requests and other questions
  • Date: Thu, 5 Feb 2004 22:23:55 +0000

On Mon, 2 Feb 2004, Olivier Salaun - CRU <address@concealed> wrote
>Hi Chris,
>
>You're right, some service messages of Sympa are still in NLS catalogues.
>We plan to move all these strings to templates but there is still some
>work left...

Thanks for advising me of this. I've come up with a crude hack which
will get me by for now:

--- List.pm.orig Thu Feb 5 17:56:44 2004
+++ List.pm Thu Feb 5 21:46:53 2004
@@ -6619,8 +6619,15 @@
$command = "auth $keyauth $cmd $listname $param[0]";
my $url = "mailto:$robot_email?subject=$command";;
$url =~ s/\s/%20/g;
- $body = sprintf Msg(6, 260, $msg::subscription_need_auth)
- ,$listname, $robot_email, $command, $url ;
+# $body = sprintf Msg(6, 260, $msg::subscription_need_auth)
+# ,$listname, $robot_email, $command, $url ;
+ $self->send_file('auth_subscription', $email, $robot,
{'keyauth' => $keyauth,
+ 'command' =>
$command,
+ 'url' => $url,
+ 'robot_email'
=> $robot_email,
+ 'email' =>
$email
+ });
+ return 1;
}elsif ($cmd =~ /add$/){
$keyauth = $self->compute_auth ($param[0],'add');
$command = "auth $keyauth $cmd $listname $param[0] $param[1]";


but I don't see where I need to make changes to get my new
auth_subscription.tpl to be editable from the web interface. Perhaps I
should keep it simple for now and forget about such niceties until the
planned move to templates.

>
>Chris Hastie wrote:
>
>> Also, for one list in particular, I want the list to generally be
>>unmoderated but I need the ability to specify that one or two
>>troublesome individual subscribers should be moderated. Is this
>>possible with Sympa?

This I managed to crack without having to go into the main code at all,
which I just love! I added an extra field, moderate_subscriber, (enum,
'0', '1') to my subscribers table, registered it in sympa.conf and
created this scenario:

title.us restricted to subscribers, flagged subscribers moderated

equal ([subscriber->moderate_subscriber], 1) smtp,smime,md5 -> editorkey
is_subscriber([listname],[sender]) smtp,smime,md5 -> do_it
is_editor([listname],[sender]) smtp,smime,md5 -> do_it
is_owner([listname],[sender]) smtp,smime,md5 -> do_it

The only thing that maybe could have made the process easier would have
been not having to change the database structure. A third table, call it
prefs, with four fields, user, list, pref_name, pref_value, might be a
way of achieving this one day.
--
Chris Hastie



Archive powered by MHonArc 2.6.19+.

Top of Page