Old log documents are not deleted when the Agent is enabled

Problem

The agent to delete old documents was configured then enabled correctly using the options in one of the SpamSentinel databases such as Quarantine, Reporting, Logging or Policies but even after waiting over-night the scheduled agent did not remove any documents.

Background Information

Agents enabled using the forms in the SpamSentinel database are still restricted in what they can do by native Domino security restrictions and also must be run on a schedule by the Domino Agent Manager server task.  The Notes ID used in the Agent configuration button in SpamSentinel becomes the 'Agent Signer' when the agent is enabled or disabled.

Solution

1.  Check the Domino server where the database are located to ensure that the Agent Manager server task is actually running.  

If it is not running, you can start it by sending this command to the Domino server: load amgr  

You can also check the Domino server's notes.ini file to see if the Agent Manager is configured to load when Domino is started by looking at the SERVERTASKS= line.

2.  Check to see if the Agent Manager is keeping up with its own schedule.

Sometimes this server task can encounter errors where it is running but gets 'stuck' so that no agents are actually triggered. Issue this command to the domino server and check to see if the results look correct: tell amgr sched

If agents are not being run on time, you may need to forcibly restart the Agent Manager task or even restart Domino:

3.  Check the database ACL.

Verify that the ACL of the SpamSentinel database gives Delete privileges to the Notes user who clicked the hot-spot to enable the agent.  If that privilege is missing, add it.  This must be repeated for each SpamSentinel database in which that the same user enabled a document deletion agent.

4.  The user who enabled the agent must also have the appropriate rights within Domino to run LotusScript agents. 

View the Domino server configuration document and locate the Security settings for running agents. Ensure the user who enabled the agent is listed either explicitly or is included through membership in a Group.