This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
LDAP cleanup in config.php #4536
Labels
1. to develop
Accepted and waiting to be taken care of
documentation
Improvements or additions to documentation
good first issue
Small tasks with clear documentation about how and in which place you need to fix things in.
help wanted
Extra attention is needed
needs info
Not enough information provided
papercut
Annoying recurring issue with possibly simple fix
I was really confused when I started receiving bounced e-mail errors for the daily Nextcloud notification mail for a user that I had removed from our company (incl. the e-mail) and our nextcloud.
A lot of bounced e-mails would also eventually damage our domain's spam rating so I tried to find where in NC that e-mail address was still present.
After some time I actually found the problem and a solution: The LDAP database in NC doesn't cleanup after itself automatically. So when you delete useres via LDAP they still stay somewhere in the NC database.
The solution is quite simple:
As described here:
https://docs.nextcloud.com/server/latest/admin_manual/configuration_user/user_auth_ldap_cleanup.html
You just have to add
'ldapUserCleanupInterval' => '51'
to the nextcloud config.php
Could this be implemented as default into the AIO NC containers config.php? or would this cause a problem if LDAP isn't activated?
The text was updated successfully, but these errors were encountered: