Skip to Content.
Sympa Menu

en - [en@sympa] Trouble with the SOAP API

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Matthias Mörstedt <address@concealed>
  • To: "address@concealed" <address@concealed>
  • Subject: [en@sympa] Trouble with the SOAP API
  • Date: Thu, 12 Feb 2026 13:52:19 +0000

Hi there,
I got stuck on a couple of things using the SOAP API:
I have a list address@concealed and a domain listmaster to connect via the soap api.

#1 triggering the double optin 
"add"ing a user via soap to the list with the domain listmaster does not trigger the doubleoptin process. From what I recently read I might need to use a user with less rights, but then again I can't use the soap api with less rights?

#2 passing the hostname
the productive system seems to have a problem with all the other host names.
  #Apache Config
  ScriptAlias /sympasoap /usr/libexec/sympa/sympa_soap_server-wrapper.fcgi
  <Location /sympasoap>
    ProxyPreserveHost On
    SetHandler "proxy:unix:/var/run/sympa/sympasoap.socket|fcgi://"
    Require all granted
  </Location>

Login via SOAP works fine, with or without a <robot/> directive, but everytime I'll add a user to address@concealed
I get the error in the logs:
Feb X 12:08:50 maindummy sympasoap[21941]: info Sympa::WWW::SOAP::add(list = address@concealed, email = address@concealed, quiet = 0) From via proxy application  

which of course results in an error 500, as the list is not recognized. Using the full listname only results in:
address@concealed@otherhost.dummy.dev 

Any idea where the host information is getting lost? Adding a <robot /> to the soap call doesn't help.

Cheers,
Matt


  • [en@sympa] Trouble with the SOAP API, Matthias Mörstedt, 02/12/2026

Archive powered by MHonArc 2.6.19+.

Top of Page