Christopher Pax | 8 Jun 18:13 2011

edit permissions for editfile page

We have taken away most of the permisssion people get on our lists. one 
of them is the ability to use the page for editfile, that customizes 
welcome and deletion messages. but for one list we want to grant the 
owners this ability.

how do i do that?

--

-- 
Christopher Pax
University Information System
New Jersey Institute of Technology

Max-Florian Bidlingmaier | 9 Jun 11:37 2011
Picon

Variables in config.tt2 for automatic list famlies


Hello,

I'm just working my way to atomatic genrated lists using families. So my
problem is i need the full mailaddress of the list for a ldap lookup. [%
listname %] works for the local part. But I found no way to get the
domain name.Variables from
http://www.sympa.org/manual/list-definition#list_template_files does't
seem to be valid in this context. So my question. Which varibales are
available in this context and is there any chance to get the full
address the mail has been send to (list's mailaddress)?

greets
max

config.tt2:
------------snip-----------
user_data_source include2

owner
email owner@...
gecos Whateveer
info someinfo
reception nomail

subject Test

include_ldap_2level_query
host localhost:389
user cn=postfix,ou=administratives,dc=lan
(Continue reading)

christopher pax | 14 Jun 15:45 2011

permissions for customized messages

For one of my lists a owner has requested that they be able to customize messages like subscribe message, or welcome message.
Normally we do not allow this.
How can I enable for just one list?

I know it has something to do with edit_list.conf...


samer khalil | 14 Jun 19:11 2011
Picon

distribute mail

Hi,
We are not able to distribute individual emails after moderation. send type is (moderated) editorkey
From the web interface  we get the message "distribute: action will complete soon)
In the mail log the message is sent to sympa <at> [robot] instead of the list members.

Related logs in sympa.log:

on message sent to the list:

Jun 14 20:07:48 tux sympa[16473]: notice main::DoFile() Processing /home/sympa/spool/msg/mylist-nq9PcUkTWzdbib83Gx3rj0ZCPvBGgIZfGVVtcWQMv48@public.gmane.org ; sender: "Unauthenticated AUBnet User" <acad_proto-nq9PcUkTWzeZUscwuGhMSg@public.gmane.org>  ; message-id: <20110614200744.17885mm4hrwhyyqo <at> imail.aub.edu.lb>  
Jun 14 20:07:48 tux sympa[16473]: info main::DoMessage() Processing message for mylist with priority 5, <20110614200744.17885mm4hrwhyyqo-pyWbPgl4h9blUXfzFf7Abg@public.gmane.orgu.lb>  
Jun 14 20:07:49 tux sympa[16473]: info Auth::create_one_time_ticket() Auth::create_one_time_ticket(std_proto-nq9PcUkTWzeZUscwuGhMSg@public.gmane.org,aub.edu.lb,modindex/mylist,mail) value = 1167066665703 
Jun 14 20:07:49 tux sympa[16473]: notice List::send_to_editor() ticket : 1167066665703 
Jun 14 20:07:49 tux sympa[16473]: info main::DoMessage() Key bec812b2f1205babaa5525c1dcc99cc4 for list mylist from acad_proto-nq9PcUkTWzeZUscwuGhMSg@public.gmane.org sent to editors, /home/sympa/spool/msg/mylist-nq9PcUkTWzdbib83Gx3rj0ZCPvBGgIZfGVVtcWQMv48@public.gmane.org 


on message viewed by moderator:

Jun 14 20:08:04 tux wwsympa[16533]: info [robot aub.edu.lb] [session 75449764918418] [client 192.168.1.15] [user std_proto <at> aub.edu.lb] main::do_ticket() do_ticket(1167066665703) 
Jun 14 20:08:04 tux wwsympa[16533]: info Auth::get_one_time_ticket() xxxx Auth::get_one_time_ticket(1167066665703) : result : success 
Jun 14 20:08:04 tux wwsympa[16533]: info [robot aub.edu.lb] [session 75449764918418] [client 192.168.1.15] [user std_proto-nq9PcUkTWzeZUscwuGhMSg@public.gmane.org] [list mylist] main::do_modindex() do_modindex 
Jun 14 20:08:04 tux wwsympa[16533]: info [robot aub.edu.lb] [session 62844526585762] [client 192.168.1.15] [user std_proto-nq9PcUkTWzeZUscwuGhMSg@public.gmane.org] main::do_ticket() do_ticket(1167066665703) 
Jun 14 20:08:04 tux wwsympa[16533]: info Auth::get_one_time_ticket() Auth::get_one_time_ticket: ticket 1167066665703 from std_proto-nq9PcUkTWzeZUscwuGhMSg@public.gmane.org has been used before (14 Jun 2011 at 20:07:49) 
Jun 14 20:08:04 tux wwsympa[16533]: info Auth::get_one_time_ticket() xxxx Auth::get_one_time_ticket(1167066665703) : result : closed 
Jun 14 20:08:04 tux wwsympa[16533]: info [robot aub.edu.lb] [session 62844526585762] [client 192.168.1.15] [user std_proto-nq9PcUkTWzeZUscwuGhMSg@public.gmane.org] main::do_ticket() do_ticket(1167066665703) : Refusing to perform login because the ticket has been used before 


on message approved and distributed:
Jun 14 20:08:17 tux wwsympa[16533]: info [robot aub.edu.lb] [session 13071376630028] [client 192.168.1.15] [user std_proto-nq9PcUkTWzc@public.gmane.orglb] [list mylist] main::do_distribute() do_distribute(bec812b2f1205babaa5525c1dcc99cc4) 
Jun 14 20:08:17 tux wwsympa[16533]: info [robot aub.edu.lb] [session 13071376630028] [client 192.168.1.15] [user std_proto-nq9PcUkTWzeZUscwuGhMSg@public.gmane.org] [list mylist] main::do_modindex() do_modindex 
Jun 14 20:08:18 tux wwsympa[16533]: info [robot aub.edu.lb] [session 11546551530477] [client 192.168.1.15] [user std_proto-nq9PcUkTWzeZUscwuGhMSg@public.gmane.org] main::do_home() do_home 
Jun 14 20:08:19 tux sympa[16473]: notice main::DoFile() Processing /home/sympa/spool/msg/sympa-nq9PcUkTWzdbib83Gx3rj/DysDqeanavpXxYI+GPP/o@public.gmane.org ; sender: std_proto-nq9PcUkTWzeZUscwuGhMSg@public.gmane.org  ; message-id: <sympa.1308071297.16533.632-nq9PcUkTWzeZUscwuGhMSg@public.gmane.org>  
Jun 14 20:08:19 tux sympa[16473]: info main::DoSendMessage() Processing web message for sympa-nq9PcUkTWzeZUscwuGhMSg@public.gmane.org 
Jun 14 20:08:19 tux sympa[16473]: info main::DoSendMessage() Message for sympa-nq9PcUkTWzeZUscwuGhMSg@public.gmane.org sent 


as u can see the message is sent to sympa-nq9PcUkTWzeZUscwuGhMSg@public.gmane.org instead of mylist members
Any suggestions on things that may be causing this behavior?

thanks,
Samer
Adam Bernstein | 16 Jun 02:58 2011
Picon

Re: Sympa hung processing digest with 100% CPU

Following up again on this:

>> For example, in messages sent to moderators, the mailto URL:
>> <mailto:sympa@...?subject=DISTRIBUTE%20listname%20a1d3bfecb352515c3bc62f19fb5a4c0a>
>>
>> becomes:
>> <mailto:sympa@...?subject=DISTRIBUTE%20listname
>> %202590b1030dcdf3b12be59a88d2a2eab9>
>>
>> thus preventing users from clicking it to distribute a message.

Although that indication of unwanted side-effects led us to remove 
Marc's patch, continued instances of this bug crashing our Sympa server 
and creating unhappy users has led us to put it back in.  After all, an 
extra linebreak or two here and there is a pretty minor matter, whether 
it's in a command URL or elsewhere, while crashing the server is a major 
problem.  Users can always paste a broken link back together if necessary.

But, David et al., is there any hope of an approved and permanent fix to 
this bug?  Pretty please, with a cherry on top?

     adam

Thoralf Schulze | 16 Jun 10:36 2011
Picon

prevent status mails for moderated lists

hi there,

is there any way to have sympa (6.0.1 from the debian squeeze repos) not send out status mails for
non-members of moderated lists (send privateoreditorkey)?

to be more precise, i'm talking about the "Your message to the list %listname% has been forwarded to the
moderator(s)" messages sent to non-subscribers of %listname% - these messages are rather annoying if
the sender itself is a mailing list. i've been sifting through the templates, but couldn't find a matching
entry - the string itself seems to appear only in /usr/lib/sympa/locale/en_US/LC_MESSAGES/sympa.mo
or its localised counterparts.

for the time being, i hacked /usr/lib/sympa/bin/sympa.pl directly to get the desired behaviour - but that
is certainly not the right way of doing it. i'm looking forward to hear about more elegant solutions :-)

thank you very much,
thoralf.

David Verdin | 17 Jun 14:57 2011
Picon

Re: prevent status mails for moderated lists

Hi Thoralf,

Le 16/06/11 10:36, Thoralf Schulze a écrit :
is there any way to have sympa (6.0.1 from the debian squeeze repos) not send out status mails for non-members of moderated lists (send privateoreditorkey)?
Yes. Change the scenario to add the "quiet" option.

The distributed scenario looks like this:

is_subscriber([listname],[sender]) smtp,dkim,md5,smime    -> do_it
is_editor([listname],[sender])     smtp,dkim,md5,smime    -> do_it
true()                             smtp,dkim,md5,smime    -> editorkey

Change it to:

is_subscriber([listname],[sender]) smtp,dkim,md5,smime    -> do_it
is_editor([listname],[sender])     smtp,dkim,md5,smime    -> do_it
true()                             smtp,dkim,md5,smime    -> editorkey,quiet

Regards,

David

P.S.: More details on the authorization scenarios: https://www.sympa.org/manual/authorization-scenarios
to be more precise, i'm talking about the "Your message to the list %listname% has been forwarded to the moderator(s)" messages sent to non-subscribers of %listname% - these messages are rather annoying if the sender itself is a mailing list. i've been sifting through the templates, but couldn't find a matching entry - the string itself seems to appear only in /usr/lib/sympa/locale/en_US/LC_MESSAGES/sympa.mo or its localised counterparts. for the time being, i hacked /usr/lib/sympa/bin/sympa.pl directly to get the desired behaviour - but that is certainly not the right way of doing it. i'm looking forward to hear about more elegant solutions :-) thank you very much, thoralf.

--
David Verdin
Comité réseau des universités

Due to the limitations of human brain, I fail to remember all the mails.
So if you want your bug reports or feature requests for Sympa to be processed, please post them to the Sympa tracker
Attachment (smime.p7s): application/pkcs7-signature, 7555 bytes
David Verdin | 17 Jun 14:58 2011
Picon

Re: Sympa hung processing digest with 100% CPU

Hi Adam,

Yes, there will be a permanent fix soon. No details yet, I still have to figure out whether the problem come from Sympa or the CPAN module. I'll keep the list updated about it.

Regards,

David

Le 16/06/11 02:58, Adam Bernstein a écrit :
Following up again on this:

For example, in messages sent to moderators, the mailto URL:
<mailto:sympa <at> cru.fr?subject=DISTRIBUTE%20listname%20a1d3bfecb352515c3bc62f19fb5a4c0a>

becomes:
<mailto:sympa-gEzMqofSdz4@public.gmane.org?subject=DISTRIBUTE%20listname
%202590b1030dcdf3b12be59a88d2a2eab9>

thus preventing users from clicking it to distribute a message.

Although that indication of unwanted side-effects led us to remove Marc's patch, continued instances of this bug crashing our Sympa server and creating unhappy users has led us to put it back in.  After all, an extra linebreak or two here and there is a pretty minor matter, whether it's in a command URL or elsewhere, while crashing the server is a major problem.  Users can always paste a broken link back together if necessary.

But, David et al., is there any hope of an approved and permanent fix to this bug?  Pretty please, with a cherry on top?

    adam

--
David Verdin
Comité réseau des universités

Due to the limitations of human brain, I fail to remember all the mails.
So if you want your bug reports or feature requests for Sympa to be processed, please post them to the Sympa tracker
Attachment (smime.p7s): application/pkcs7-signature, 7555 bytes
Christian Schroeder | 15 Jun 10:14 2011
Picon

Disable new user registration on web frontend

Hi,

this is propably simple, but I did not manage to find any information
about this issue:

After installing sympa on debian lenny, the webfrontend allows anyone
(=world) to register.
I would rather prefer that only registered used (which I have added
manually, are able to use the web frontend).

Of course, one could use control the access via Apache means and
an identical authentication system for apache and wwsympa (such as LDAP).
But then, my users would have to login twice.

Removing the register Button "Firtst login?" in login_menu.tt2 is even
less elegant.

I am pretty sure there must be some inherent functionality to disable
public registration and turn it into a closed group. This should
be true for the entire server not only for certain lists.

Could someone please give me a clue how to proceed in order to implement
my requirements?
Thank you very much.

Cheers
Christian

David Verdin | 17 Jun 15:25 2011
Picon

Re: permissions for customized messages

Hi Christopher,

Le 14/06/11 15:45, christopher pax a écrit :
For one of my lists a owner has requested that they be able to customize messages like subscribe message, or welcome message.
Normally we do not allow this.
How can I enable for just one list?

I know it has something to do with edit_list.conf...
Bingo. ;)

You can add, in edit_list.conf. Some entries stating explicitely what files a user can edit.
For example, if you have the following line in the config:

welcome.tt2        owner,privileged_owner        write

Then the owners and privileged owners can edit the welcome messages.

What's dumb is that it is not explicit in the web interface : In the "Customizing" tab, you will always have the full list of files you can edit with the "edit" button next to them, Even if you won't be able to really edit them. You will just be displayed an error message if you try to click on the "edit" button.

It is not that bad, as you can edit the template for the list and simply remove the entries corresponding to the files for which you don't want to let the users edit.
Not sure that the sentence above is very English...

Regards,

David



--
David Verdin
Comité réseau des universités

Due to the limitations of human brain, I fail to remember all the mails.
So if you want your bug reports or feature requests for Sympa to be processed, please post them to the Sympa tracker
Attachment (smime.p7s): application/pkcs7-signature, 7555 bytes

Gmane