Developers of Sympa

[Olivier Salaün - CRU <address@concealed>]

Hi,

We wish to integrate your extensions to the product but it will require a few changes on our side :

1. getListConf() and setListConf() should check the edit-list.conf setup before allowing a user to view/modify list parameters
2. the setListConf() subroutine might possibly break a list if provided parameters are incorrect. If would be interesting to check the client SOAP program if you can provide pieces of it...
3. createList() should use the newly created admin::create_list() subroutine

Could you please add an entry to our feature/bug tracking system, so we keep track of your extensions to the soap server :

http://listes.cru.fr/mantis/

I can't tell you when we can find some time to work on the SOAP server extensions....

Thank you for sharing your work !

PS: it seems that the 'welcome' problem has been fixed in the 5.x versions that now use TT2 template format.

epsas wrote:

Apologies for getting back to this list so late - 

I have been integrating sympa into Flexomatic, our social networking application.  The sympa soap we are using is located at:

http://www.dogsquad.co.uk/~epsas/sympasoap.pm 

anybody need help using sympa+soap?

You can check out our mailing list interface at http://beta.indyvoter.org -- we are already using sympa to create and manage our mailing lists over SOAP!  It is a great thing!


List::send_file - Not sure if this is a bug...  If a user creates a mailing list called "welcome", it will prevent sympa from reading the default "welcome" template.  This is because $Conf{'home'}/$action is included in the template file search list.  Is there any reason for the expl/ directory to be included in send_file's search list?  

    [...]
  

-- 
Olivier Salaün
Comité Réseau des Universités
-------------------------------------------
Validation signature / Trusting  signature: --> http://igc.cru.fr/trust.html
------------------------------------------- 

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature