On 2014-05-03 23:55, Mark Sapiro wrote: >> I can't say more about what to do without actually seeing your >> MemberAdaptor, however you might look at >> <https://bugs.launchpad.net/mailman/+bug/558106> for an alternative.
That was actually my starting point to develop my MemberAdapter. I did not use it directly because the LDAP server might be down sometimes and I still wanted mails to be delivered. I did not want to try LDAP replication, partly because it seems complicated and partly because I do not want the LDAP database on the webserver (even if the login passwords are hashed). > OK, I took a quick look at your stuff from > <http://sourceforge.net/projects/ldapsync/files/>. > > I think your issue is you rely on extend.py to instantiate > FileMemberships and reload the member data when the list is instantiated. > > I suspect your Mailman is 2.1.14 or older which maintains a list cache > in the qrunners so the list gets instantiated and cached and further > references to the list object retrieve it from the cache and update it > as needed, but it is never again actually instantiated so extend.py is > never called again. > You are right, it is mailman 2.1.13-5, I am running a debian server. After upgrading to debian wheezy with mailman 2.1.15-1, the problem seems fixed. Thanks. regards, Viktor P.S: It is not wise to register to a mailing list using the address of another mailing list. I actually replied a few days ago, but I used 'reply to all' and that only send an e-mail to myself and the other administrator. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
