The mailing list for listmasters using Sympa

[Benoit Hamet <address@concealed>]

Hi All, Hi Lennon,

I wrote an external application (to be clear, a small app in
phpgroupware) that permit some actions against sympa. The first plan was
to use the SOAP API, which is ok to get the cookie for example, but, as
you said, is (still) limited for more real work. so we are interested by
such an evolution of the SOAP Api, because actually, I do something very
dirty, like posting to the wws interface using curl (under php). So I
wrote some general purpose things to create / modify the list, and use
ldap as the sources for list, which correspond to groups in our
phpgroupware installation. So it would be better if we were able to
manage completly sympa from SOAP, when we need to update info of list
(even if suscribe / unsubscribe is done by adding/removing people from
groups).

So AFAIK at least 2 "installations" here should benefit of SOAP api
improvement : the "ProGET" Collaborative system project
(http://proget.int-evry.fr) (GET internal collaborative system, based on
phpgroupware / sympa / twiki), and another derivative of phpgroupware
named picolibre (http://picolibre.org) (a mini sourceforge like plateform).

So If you want more infos, you can ask me directly, but we will be happy
for such an improvement.

Regards,

Benoît Hamet.

Lennon Day-Reynolds wrote:
> I've been working on an application for use on our campus to allow 
> users to easily subscribe and unsubscribe from a set of public lists, 
> calling the Sympa SOAP interface from a Ruby on Rails web UI.
> 
> In doing so, I've come up against a number of limitations of the 
> current SOAP API, including the extremely limited information about 
> each list made available to SOAP clients. Looking forward, I think  our
> application would benefit greatly from an extended API with  several new
> methods and an enriched 'ListType' that included a number  of
> currently-missing fields -- list owners, description, and  subscription
> policy, to name a few.
> 
> Before I begin any major development on this, though, I wanted to  gauge
> the level of interest others (including the Sympa maintainers)  would
> have in such an extension. I realize that the SOAP API has been 
> somewhat of a second-class interface to date, and I don't want to  spend
> a lot of time and effort trying to enrich it if there simply  isn't
> going to be demand for it outside our institution.
> 
> Alternately, if other people have worked more extensively on driving 
> Sympa installations via external user interfaces, I'd be interested  to
> hear what worked for you.
> 
> Thanks in advance,
> 
> Lennon Day-Reynolds
> System Support Specialist
> Reed College
>