Auto/extended away timers trigger reconnect of offline client
It appears that the "away after" or "not available" timers can trigger a client in an "offline" state to come back online. The issue can be reproducing by doing the following:
-
Connect via MachineA as user@foo.org/home.
-
Connect via MachineB as user@foo.org/laptop.
-
From MachineB, send an ad-hoc command for MachineA's client (home resource) to go "offline". This must be done before MachineA's client is in "Not Available" state.
-
Observe as MachineA comes back online when the "away after" or "not available" timers are triggered.
I suspect this would apply to all OSes and should be fairly easily to reproduce.