The mailing list for listmasters using Sympa

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

Hi Anthony,

The format of auth.conf has evolved in Sympa 4.x. You should now explicitely tell Sympa that it is allowed to manage its own passwords. Here is the related entries in the release notes :

*****    auth.conf format has changed ; if you had a previous auth.conf file you
*****    should change it according to the new format

You should add the following paragraph at the end of your existing auth.conf :

user_table
regexp                 .*

We will add more log to warn about this...

Anthony Hess wrote:

This is a problem I am having getting both ldap and user_table auth to work at the same time.  Its sort of related to the other issue I sent, but I believe it separate thus the separate email.

I upgraded sympa a year ago from 3.3.x to 4.x.  Originally this caused my ldap auth to break (taking the archiving along with it).  This problem was solved when I upgraded to the latest 4.x branch (4.1.5 I believe), but suddenly people in the user table could no longer log in (so, people in ldap couldn't log in before, now its people in user_table).

[...] This auth.conf is the one that just checks ldap:

ldap
        host fugazi.engr.arizona.edu:389
        suffix ou=People,dc=engr,dc=arizona,dc=edu
        bind_dn cn=proxyagent,ou=profile,dc=engr,dc=arizona,dc=edu
        bind_password I_have_the_bind_password_here
        scope one
        timeout 10
        get_dn_by_uid_filter (uid=[sender])
        get_dn_by_email_filter (mail=[sender])
        email_attribute mail
        alternative_email_attribute email
  

[...]

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