Cleaning Up The System Address Book

[thecowster]

Hi there,

I wonder if there's some command I can use to regenerate the system address book from the scalix users known to omshowu?

We have over time accrued a number of dead records - which omshowu does not report, but omsearch does. omdelent successfully removes these. These dead records were created by either a failed omaddu, or by a failed omdelu.

Our user list (and therefore address book) are being maintained by an internally written sync script, which looks at our group's LDAP and creates local and "internet" users based on that. As this process is automated, we also want to automate cleaning up the system address book when these dead records are created. Is there a command to do this? Of course, (yet another) script could be written which compares the results of an ldapsearch with omshowu, and calls omdelent for each missing entry - but we'd rather avoid re-inventing the wheel)

Cheers
TheCowster

[dirk]

The entries displayed by omshowu are from the hidden userlist directory. If we dont have entries in SYSTEM that have been created by directory synchronisation we can assume that the search filter "ENTRY-TYPE=1" against the SYSTEM directory only shows entries that are mailboxes (and should therefore appear in USERLIST).

But I would rather recommend to see if the source of the problem can be found. Such workarounds may go wild at some point.
From my experience these stale entries should not appear that often with current Scalix releases. There is still a chance to force the occurence by forcefully killing a running omdelu or omaddu or when deleting extremely large mailboxes through SAC. But this is surely not something what I would try to workaround with a frequently running cleanup script.

Best Regards,
Dirk

[thecowster]

But I would rather recommend to see if the source of the problem can be found.

Unfortunately this morning I used omdelent to get our system directory back in sync with omshowu /SAC - so the dead records are already gone However, if/when this occurs again I will update this ticket with details.

Cheers
TheCowster