How to you prevent multiple parallel execution of the server agent?
I implemented something similar to this by a small agent that was started by RunOnServer and did nothing else than a tell amgr run...
Based on experience the users will press the button over and over because
they don't get an immediate response.

So the log.nsf reaches its threshold, is deleted and recreated. And where are my log entries from this morning that I need to analyse a problem?
I feel it is a pretty stupid idea to delete the data. A better solution would be to rename the current database by extending the file name with a suffix like timestamp or a running number and then create a new empty database.
Then you are free to apply your own ways of handling this renamed databases.

If the mails are created on the external server, disable the router task on this server. Make the mail.box a replica of the one of the internal server. Mails created on the external server will be replicated to the internal server's mail.box and the internal router task will forward the mail. We used this at a customers installation for some years until they decommissioned their external server.

In some jurisdictions this would constitute illegal user activity tracking

In my experience the common user is just too ignorant to edit any settings or move archives

make ODS more robust und fix fixup. We often had the case that after a server crash databases are corrupted bejond repair. Fixup just gave up. Also, server/applications crash because of faulty documents but fixup is unable to correct or even find them.

This sounds very tricky because of the wide choice of possibilities to check.
An easier way would be a place where ( if auto-select is configured), an admin written piece of LotusScript code executes and decides what to do.
This is much more flexible than a fixed set of available choices where, as usual, the one you need is missing :-)

I don't think they will ever change the catalog task. About 5 years ago we submitted an enhancement request to include the settings for mail quota and warning threshold. The request was declined.

According to the online help:

@Domain
Returns the name of the current user's Domino mail domain listed in the current location document of the Personal Address Book.

As the domain is not part of the ID file but taken from elsewhere, it could be forged too easy.

Giving Editors (=Users) the ability to unlock is like putting the fox in charge of the henhouse.

This is already available for LotusScript. Have a closer look at Sub Terminate().

I think the server's log.nsf is the wrong place. The messages have nothing to do with the server and the log should be kept clean of messages not related to the server.

The current implementation in Lotusscript (Java) should NOT change to prevent the break of existing code. There should be an aditional property showing the physical size

This is plain application logic and I think this should not be part of the replicator.

If we ever will get an overhauled workspace, please provide an official API to manipulate it.

This would breach security as it would be possible for non-authorized persons to read the About Document.

Why?

Add a second option "Run on server with remote debugger"

Why not just fix the obviously broken way how caching iworks?

I think the date and time format displayed should depend on the client displaying it and not on some server setting.

I think that any developer responsible for such stupid error messages should be flogged :-)

In a multi server environment, updating the group documents would lead to a high number of replication conflicts.