Hi,
After goin throug all the forums related to Out of Office , still my problem seems to be no end. I have clustered domino servers in which OOO agent doesn’t seem to be workin… Users enable it and still it doesn’t get enbled on the server side…Second case is even the one which is enabed as we see it on the server agent, the out of office messages are not being sent to the recipients…
Please help me out.
Subject: Out Of Office Issues
Accessing from Local or server replica?Mail file owner access is set to editor or manager?
If the user’s name in the mail file ACL is set to editor, an adminP request is used to enable the OoO agent in the user’s mail file on the mail server. Check admin4.nsf for request status/errors. Check admin4.nsf and its documents are replicating to all servers.
If the user’s name in the mail file ACL is set to manager the OoO agent won’t use adminP and should enable straight away, and if other settings are correct, see below.
Check the OoO agent is scheduled to run on the same server as the user’s primary mail server and not local.
Check your Domino server’s document, security settings, allow your users and the signed OoO agents, to run agents.
Check the signature (functional ID?) that signed the OoO agent has the permissions to run and its certificate has not expired.
Check amgr & adminp are running as server tasks.
Consider using, Tell adminp process new, to trigger unprocessed requests.
Run the OoO and look for server side errors.
Tell Amgr Run “mail<mailfile>.nsf” ‘OutOfOffice’
Examine the OoO profile, in the user’s mail file, using NotesPeak.
You could write an agent that clears the ‘Notified’ and or ‘AlreadyNotified’ field in the OoO profile too.
Subject: RE: Out Of Office Issues
I have the same issue over here… If you do an ‘tell amgr schedule’, you see the OOo agent scheduled. On the cluster server you do not see the OOO schedule. Perhaps there is the problem.
In the replica of the mailbox you will see that the OOO is enabled.
Does anyone know how to deal with this?