I see the same issue in 3.0.11, unfortunately. On Jun 24, 2004, at 6:25 AM, jeff rak wrote: > I believe this issue was fixed in 3.0.11. I had the same problem in > 3.0.10 but > it magically disappeared when I upgraded ;-)