>One thing I always do here is refresh and read the posts that have come in while I've been logged in before leaving. That seems to handle the problem, but I do wish that the UT would remember where I was when I last refreshed rather than when I log out.

In order to do that, which is was CIS was offering would be to keep a User-Message table to know what has been read. That formula didn't work that long before it doesn't necessarily mean a message not read is one I would want to read. However, there was some options in some navigators which were allowing to make a bunch of messages as read. In the way people work on UT, this wouldn't serve that much. This is why we are offering a bunch of options, the most popular one is the Time Warp, to go back in time a little bit. In there, as requested, we added one to simulate the last refresh and another one to simulate the last login. That helped to achieve the mentioned goal. But, I am always opened to new suggestions in regards to that.