Op 11-12-2023 om 09:07 schreef qhivert ([email protected]):

Hello,

Probably the user is still in your sogo database, in the table SOGoProfileURL, usually   “sogo_user_profile”?

SELECT * from sogo_user_profile WHERE c_uid = “[email protected]”;
If yes, remove the row. The c_uid may be only test2.

Quentin

Thanks Quentin, I will test it asap.

Is it an idea to add a new option "remove-profile" to sogo-tool?

- Kees.


*From:*[email protected] <[email protected]> *On Behalf Of *Kees van Vloten
*Sent:* samedi 9 décembre 2023 13:27
*To:* [email protected]
*Subject:* [SOGo] Remove user profile completely

Hi all,

I am seeing errors in the dovecot logging, like this:

Dec  3 19:50:02 strauss dovecot: auth: Master user logging in as [email protected] <mailto:[email protected]> Dec  3 19:50:02 strauss dovecot: auth: ldap([email protected],127.0.0.1 <mailto:[email protected],127.0.0.1>,<XaANeJ8LbM5/AAAB>): unknown user

The logging is repeated every 5 minutes and the master user is only used by sogo, i.e. that is where the source of the issue is expected.

Sogo has some cron scripts, one of which is:

# Vacation messages expiration
# The credentials file should contain the sieve admin credentials (username:passwd) */5 * * * *    sogo    /usr/bin/timeout 4m /usr/sbin/sogo-tool update-autoreply -p /etc/sogo/sieve.creds > /dev/null 2>&1

Aparently this runs every 5 minutes and uses the master user via 'sieve.creds'.

Further more the 'test2' user is no longer an existing user in the LDAP (Samba4) OU for users. This test-user simulates somebody who has left the company.

Since the test2 user is not explicitely removed from sogo, it still has a sogo profile in the database (postgresql).

How can I prevent 'sogo-tool update-autoreply' from going over past users?

My suggestion would be to remove its user profile completely, what is the command to do so?

Or is there a better solution to this issue?

I did find 'sogo-tool remove <user>' in the documentation, it states: "Remove all folders (Calendar and Address Book) and Preference settings of a user.". I guess this is not equal to: "remove user from database", or is it?

- Kees,

Reply via email to