> It should have been fixed several > months ago (before 1.5 was released), sorry, indeed solved in 1.5! i tend to rarely update (our production servers) and should have checked against the current version. ralf