GitLab

here some spec about sympa plugins

sympa service tab : -> add a flag for allowing or not sympa alias modification ( in fact symp aalias must be generated by sympa mailing list management) -> ldapAttribut : sympaServerManaged FALSE ( alias managed by Sympa Server) / TRUE (alias managed by FD)

symap alias -> add field : -> sympaListModerator : Multivaluate (contain email address of List moderator) : type MAIL -> sympaListOwner : Multivaluate (contain email address of List Owner) : type MAIL -> sympaListTopic : Multivaluate (contain topic where list belong to) : type STRING -> sympaListDescription : Monovaluate (contain Description of list) : type STRING -> sympaListScenarioVisibility : Monovaluate (contain name of visibility scenario of list (public, only intranet) : type STRING -> sympaListScenarioSend : Monovaluate (contain name of send scenario of list (send to all subscribe) : type STRING -> sympaListScenarioAccess : Monovaluate (contain name of Acces scenario (public, onlySubscriber) : type STRING

some comment :

all scenarii are specific to sympa installation ( they could be added by administrator) all those information should be fetched by perl script when writing ldap alias ( in debian installation, config fiel of a list is stored in /var/lib/symp/expl//config : see https://www.sympa.org/manual_6.3/mail-aliases?s[]=ldap&s[]=alias&s[]=manager#alias_manager

In case of sympa diffusion list are maitain by FD ( and not by sympa) use of SOAP method is mandatory : https://www.sympa.org/manual/soap#supported_functions

(from redmine: issue id 2180, created on 2013-03-24)

• Custom Fields:
  • Bug in version: 1.0.5
  • Support contract: None