The mailing list for listmasters using Sympa

["Lorenz, Sabine (SCC)" <address@concealed>]

Hi Marco,

you should consider that the parameter ssl_ciphers is case-sensitive.
We had the same problem you describe when our setting was ssl_ciphers=All 
instead of ssl_ciphers=ALL .

Best regards,
Sabine

> On 25/08/16 10:04, Marco Gaiarin wrote:
>  Aug 24 17:39:34 armitage task_manager[1397]: err LDAPSource::connect() 
> Unable to connect to the LDAP server
> 'ldap.corsi.localdomain'
> 
> Your Sympa server is failing to connect to LDAP.  All other things follow 
> on from this.
> 
> Assuming that the hostname, and bind credentials, are unchanged in the 
> configuration, you may now have slightly different auth
> requirements defined on your new LDAP server.  In particular, you might 
> like to check the certificate being used for LDAPS -
> possibly it is self-signed or unexpectedly weak, or expired, and the 
> connection from Sympa is being a bit more strict on the
> authentication?
> 
> You can set ca_verify=none which may help (if the cert is not signed by a 
> recognised CA).  You may also want to check your
> ssl_version and ssl_ciphers=ALL settings in case your new LDAP server does 
> not support the same or as many ciphers as the previous
> one -- possibly the new LDAP server is stricter in its requirements for 
> connection.
> 
> Steve

Attachment: smime.p7s
Description: S/MIME cryptographic signature