Out-of-the-Office webmail users

hcl-bot · October 23, 2008, 12:41pm

HiI have a problem with the Out-Of-the-office services… People that use webmail account only (Not client) can’t to disable the OOO reminder msj after they have enabled onetime

in the webmail the option is disable but everyday at 4am they are receiving this msj

“Please disable the Out-of-Office agent by selecting ‘Actions > More > Out of Office…’ and clicking on Disable button”

I was trying to fix the problem with this technote

http://www-01.ibm.com/support/docview.wss?rs=0&q1=1084373&uid=swg21084373&loc=fr&cs=utf-8&lang=

But doesn’t work…

some solution or comment?

Thank you

hcl-bot · October 28, 2008, 3:49pm

Subject: OOO command

I was reading about this command

tell amgr cancel “mail<namefile>.nsf” ‘OutOfOffice’

But doesn’t work in my case… I am using Service in least to Agent

Someone know if there is a special command in order to change to disable the OOO for one specific account?

Thank

hcl-bot · October 29, 2008, 9:24am

Subject: Solution

Well… I found the solutionIn order to fix this problem follow this procedure:

Run “tell amgr sched” on all the servers in the Domain in order to verify in what database (mail<mailfile>.nsf) is running the Out Of Office agent.
Open the database with the problem (mail<mailfile>.nsf) from the Domino Administrator.
Go to → View → Design. At this point the Lotus Domino Designer will be opened with the database selected.
Expand the Code section from the left side menu and double click in Agents.
Select the OutOfOffice agent from the list.
Click in Disable button and close.
Verify again the OOO agent from the server console executing: tell amgr sched.

At this point, the OOO for this specific client will be disabled.

Thank you if someone were reading to me

hcl-bot · November 13, 2008, 10:05am

Subject: OoO solution

Thank you!

I was having this problem (and some others) the past few days after upgrading from 8.0.1 to 8.0.2. I think it was an issue with some open files but I can’t say for sure. Anyhow this fixes the problem some users had post-upgrade so thanks for the detailed post.

Richard