OOO agent - updated in mail template, does it deactive OOO agents?

HCL Domino Domino Forum
1

We are using the mail7.ntf template in a Domino 8.5.0 and Notes Client 8.5.0 environment.

We want to change the behaviour of the Out-Of-Office agent. Currently it is set to run every 6 hours, between 4am and midnight. We want it to run after the email has arrived in the user’s mailbox.

If I make the change to the agent in the mail-template, does this disable the agent that has been enabled in the users’ mailbox?

If yes, how do I implement the change and yet retain the enabled/disabled state for all users?

2

Subject: ooo after new mail

If you are in a 8x server/client environment why not push to the 8x template and enable the out of office service? It runs at the router and responds to received messages instantly:http://www-10.lotus.com/ldd/dominowiki.nsf/dx/01072009040728PMWEBSS8.htm

Otherwise…

The agent will disable and is working as designed:

http://www.ibm.com/support/docview.wss?rs=899&uid=swg21090238

It is not recommended to change the trigger:

http://www.ibm.com/support/docview.wss?rs=899&uid=swg21212467

If you must stay on a 7x template consider altering the schedule to run at a higher interval appropriate to what your server can handle. The highest interval you can set is 5 min. Generally after new mail trigger runs every five minutes. It does not run on individual emails.

3

Subject: follow-up

Upgrade to OOO service: if all servers in your mail cluster are R8+ then switching to the service sounds like a good idea.

The technotes that Rene referenced to releases prior to R8. I posted R8 documentation which highlight the changes…

4

Subject: The agent will remained enabled with some caviats

This section of Admin help goes into details:

Updating the design of an enabled agent

In pre-8.0 releases of IBM® Lotus® Domino™ , when a design update for enabled agents occurred, the agents were disabled and stopped running. This occurred because there was no mechanism to update the agent’s design and retain the original signature of the agent. In Domino 8, design update can update many enabled agents without disabling the agents.

In Domino 8, design update preserves the identify of the agent owner in the “On Behalf” field and re-signs the agent with the server ID. The agent’s enabled status is preserved only if the original agent owner has the rights to run agents and if the agent is scheduled to run on the server on which the design update is performed. The server has explicit rights to run agents only on itself. If the agent’s enabled status cannot be preserved, the design update is performed and a warning message is generated and sent to the server console as well as to the Domino Domain Manager.

For more information about using the Run on behalf of setting, see the IBM® Lotus® Domino™ 8 Designer documentation.

You may see the warning messages shown in the examples below depending on who signs the agent.

Examples

In this example, the agent was signed by the server, ServerA/DomainA, which did not have rights to run agents on the server Test/Acme. Design update updated the agent design and left the agent disabled.

Warning generated on server TEST/ACME:

Designer: Agent ‘OutOfOffice’ in ‘mail\rooks.nsf’ disabled during Design Update from template ‘mail8.ntf’. Agent signer 'ServerA/DomainA.: Users without rights to sign ‘On Behalf’ agents can only run agents on their own behalf.

In this example, the agent was specified to run on -any server-; therefore, its enabled state could not be preserved because it could not be signed with the server ID Test/DomainB ID. If the agent was signed with Test/DomainB ID, the agent would not run on any server other than Test/DomainB, which was not the intention of the agent designer. Design update updated the design of the agent and left it disabled.

Warning message generated on server Test/DomainB:

Designer: Agent ‘LotusInboxCleanup’ in ‘AdminSurvey2007.nsf’ disabled during Design Update from template ‘mail8.ntf’. Agent signer ‘Lotus Notes Template Development/Lotus Notes’.: Enabled status can be preserved only on the server where the agent is scheduled to run or, for mail agents, on the home mail server. Enabled status cannot be preserved if ‘-Any server-’ is specified for the agent.