Got the above oops when replying to support ticket 5224. I note the OP posted a reply at around the same time. Interestingly on the helpteam mailing list we have had another report where someone was replying, got an oops, went back and saw another reply. Could this be a locking issue? Cheers, Al.