Skip to Content.
Sympa Menu

en - Re: [sympa-users] Subscribers via data inclusion file

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Kolmann Philipp <address@concealed>
  • To: "address@concealed" <address@concealed>
  • Subject: Re: [sympa-users] Subscribers via data inclusion file
  • Date: Fri, 25 Oct 2013 05:03:50 +0000

hi

I understand that managing files is not preferred. How about data inclusion templates in the webend and then use them like the include files now.

 Thanks
Philipp

Philipp Kolmann <address@concealed> schrieb:

Am 24.10.13 10:48, schrieb David Verdin:
Dear all,

Le 24/10/13 00:08, Steve Shipway a écrit :
I have created a data inclusion file for querying our LDAP Server for
editor_include and owner_include.

Now I would like to use this file / template also for the subscribers.
In the web-frontend I only see the possibilities to enter all parameters
by hand again. I would like to use the data inclusion template there. Is
there a possibility?
I don't believe that this is currently a possibility (we have 6.1.14).  However, we'd also really like to have this feature as it allows you to set up the LDAP credentials but not reveal them to the list owners who use the include template.  I seem to remember asking for this previously on the Sympa-users list, so with luck it may appear in a forthcoming version...
Indeed, this is not possible for now.
Actually, the plan was even to remove entirely the datasource definition through external file and replace it by paragraphs inthe config file, even for moderaotrs and list owners.
Now that you mention it, the good aspect of this mechanism is the reusability of the datasources.
However, we have implemented list families, in which you define a config template that will be applied to all the lists of the family. That's why we wanted to get rid of the data inclusion file: we have a mechanism that allows templating for any list parameter.
I really think that the list families would be a good solution to the current problem - and you can hide passwords in the list adminsitration pages using edit_list.conf, so it is not really a problem.

Please let me know if this solution is good for you or if you see use cases where it can't apply.

Hi David,

thanks for the reply.

actually I would prefer the data inclusion. I have the same LDAP Query for editors, owners and I'd like to use it for subscribers as well.

I only need one data-inclusion file for all three purposes. On one line, I need only one (eg moderator), in another list, I might need two and in some other I might need all three of them.

How would this work with families? would I need three different families?

is the concept of families already in 6.2? I checked out the trunk and will test it later.

Thanks
Philipp


-- 
-----------------------------------------------------------------------
DI Mag. Philipp Kolmann                  mail: address@concealed
Technische Universitaet Wien                  web: www.zid.tuwien.ac.at
Zentraler Informatikdienst (ZID)                 tel: +43(1)58801-42011
Wiedner Hauptstr. 8-10, A-1040 Wien                        DVR: 0005886
----------------------------------------------------------------------- 



Archive powered by MHonArc 2.6.19+.

Top of Page