DomBlog.de - Notes, Domino and Stuff

1 - Well what can I say - going to Lotusphere and talking to the guys developing the product we work with actually pays off - cool! Jens, are you going to Lotusphere again this year?

2 - Hi,
like I already commented on Jens' original post, we are also suffering from this problem.
This is the latest update I got from Lotus last week:

"I have looked into the above SPR and have found the following. It appears that there may initially have been a delay in identifying exactly where the problem lay as the issue involves code from a number of different areas of the product such as security and design. The latest update from Development, provided yesterday, confirms that they have now identified the exact code responsible for the issue. This code was introduced some time ago, most likely as a fix for another issue, and Development now need to evaluate the exact implications of this code and the best way to correct it.

While I do not yet have exact details as to when a fix will be provided for this issue I can confirm that Development are actively investigating the issue and that due to the number of reports and seriousness of the issue this is currently one of their highest priority SPRs. "

So it looks like finally something is happening...

Thomas

3 - According to the technote and the release notes the problem has been fixed in Release 6.5.5 FP2 and 7.0.2 FP1.

4 - I still have this problem although I have patch domino with 7.02 SP1 or install new 7.0.3.