The solution was to remove users from Filr and resync them. It looks like, that the issue has shown itself, because user has been logged in before netfolders were created. After that it did not correctly sync netfolders to user.

The solution was to remove users from Filr and resync them. It looks like, that the issue has shown itself, because user has been logged in before netfolders were created. After that it did not correctly sync netfolders to user.

(Thanks Diethmar Rimser  for stepping in, I was forced offline after my first reply)

I absolutely concur with Diethmar regarding "Usually Filr is really simple", and I have pondered on how your system behaviour can have occurred since I don't want to have this happen anywhere else and knowledge means quick problem solving in those situations :).
So maybe we can all learn a bit by finding out?

My pondering got me to this: assuming you have not

• massively moved or recreated users/groups without those changes making it to the ACLs
• set rights to attributes in eDir keeping the Filr proxy account from reading group members
• massively used aliases in your configuration

, I came up with some possible triggers for this

• you had "sync group membership" unticked in "Group Settings" in the LDAP config (all Net Folders synched *before* the unticking would work fine
• you have deleted groups in eDir and re-created them with the same name without deleting/re-mapping them in Filr (then, the new group will not get synched in, the old is still there)
• you have not set up an LDAP sync schedule and group memberhips were out of sync
• you are using multiple LDAP connectors to the same tree, e.g. one for the groups and one for the users - that can cause a load of issues.

Could it have been one of those?

Thanks!
Christian