Imquotacheck -n Should Not Notify Orphan Accounts With No MailHost (Doc ID 2683618.1)

Last updated on JUNE 24, 2020

Applies to:

Symptoms

The "imquotacheck -n" command should check the mailHost and NOT notify orphans when mailHost has been removed.

The result of 'imquotacheck -n -e' continually updates "orphaned" accounts, even when the mailHost attribute has been deleted.

In this particular scenario, users are never really deleted from LDAP. When someone leaves, processing in some other database changes the LDAP mailUserStatus to deleted. A monthly script is run which looks for users with mailUserStatus=deleted and a modify time stamp more than 15 days old. The script removes the mailhost attribute. A few days later, another script is run which uses "mboxutil -o" to find orphan accounts and then deletes them.

The daily quota warning messages from "imquotacheck -n" are causing "mboxutil -o" to think the account is still active.

So, the normal periodic orphan cleanup process is failing to notice this account. Also, the size of the account is causing ISS to hang on the corresponding Index server.

It is expected that if the mailHost attribute has been removed, then "imquotacheck -n" should acknowledge that and should NOT send a warning.

The issue can be reproduced at will with the following steps:

* set the quota just over the current usage for a user (in this example, "user1" is shown)
* run: iminitquota -u user1
* send another message to user1
* "imquotacheck -u user1" shows the user is over quota and "WarnDate" is not set
* run ldapmodify to remove the mailhost attribute
* double-check that the change has gone through
* "imquotacheck -n -e" again shows it sent the user a warning message

Due to this issue, for accounts where the mailHost has been removed, 'imquotacheck -n -e' continually updates them and sends a warning which then causes "mboxutil -o" to think the account is still active.

Changes

Cause