Uh Clem's Admin World

I configured my two clustered 8.0.2 mail servers to run out-of-office as a service about 3 weeks ago.  I decided to take a look at how that was working, so I ran:

tell router O  > returned 11 users
tell amgr sched > OutOfOffice agent running for 9 users

What? I expected everyone to be running OOO as a service now.  All clients are on 8.0.2 and all mail files are on the mail8.ntf template.

It turns out that 2 criteria must be met before a mailbox will be registered to run OOO as a service:

1.  The user must have turned ON the OOO since the servers were configured to run OOO as a service.  If a user never turned off their OOO from the last time they were out and just reconfigured the dates, then it will not switch to OOO as a service.
2. The user must receive an email after turning on the OOO in step 1.  This is the trigger that tells the mailbox to stop using the agent and use the service instead.

So when you configure your OOO to run as a service, it may take a while for all the mail files to be registered to run it as a service rather than an agent.    You may need to monitor the mail files over time to see who is still running the OOO agent (using "tell amgr sched").  For them you may need to make sure they have turned off the OOO after their previous time out.

I've had about 4 users now call me to complain about their inbox text turning a pale gray as if all the entries are ghosted.  The background stays white.  Additionally it seems the scroll bar doesn't work properly.   The problem goes away if they close their inbox and reopen it.

Just one of those strange quirks.  Anyone else have this problem?   I've opened a PMR to try to get more info.