Subject: OOS notified list isn’t cleared unless the service is fully closed out…
I have a question regarding how often ooo replies are sent.
Suppose we have the following sequence:
User1 - turns on OOO (service)
User2 - sends message to user1 (gets OOO reply)
User1 - disables OOO
<If User1 or User2 (or anyone else) sends mail to User1 – to trigger OOS shutdown…>
User1 - enables OOO
User2 - sends message to user1
<Now, User2 gets a notification.>
Should user2 get another OOO reply? - Not in your steps, as written – would need to have User1 receive mail in between the disabling and re-enabling of OOS.
How is this determined? From what I have observed, user2 does not. How is it determined that he should not get a reply because he already received a previous one? Is it time based…
Hi - The out-of-office service isn’t fully closed out until the router delivers mail to the mailfile in question – after out-of-office has been manually disabled in the UI, or the OOS end time has passed. It’s at this point that the router detects the change in state, and shuts down the service. And you’ll know this has happened, because this is what generates the out-of-office summary doc. (Can also do a ‘tell router o’ on the server console, to see a list of dbs in which OOS is currently active.) Note that there’s additionally a check at 4am every day, so if a user didn’t get any mail, an OOS shutdown would be detected and carried out at that point.
In your example, OOS hasn’t actually been shut down, although the user had momentarily disabled out-of-office. The notified list isn’t cleared out until the service shuts down, so after you’ve re-enabled OOS in User1’s mailfile, your User2 is still in the active notified list, and won’t get any further out-of-office notifications.
If you were to have User2 send mail to User1 between the disabling and re-enabling of out-of-office, this would trigger an OOS shutdown, and when you re-enabled out-of-office after that, any new message from User2 would generate an out-of-office notification.