Partially Fixed ..
Apparently there’s a trojan somewhere in this account which I have yet to detect. It is triggered everytime someone attempts to post a comment (basically every time an HTTP Post command is called) .. which basically explains the 404 Page Not Found errors. It then generates a binary file which is essentially a back up of the whole blog and stores it in the CGI-Bin which eventually overloads this account’s quota.
Looks like its back to the drawing board. For the time being, comments will unfortunately have to be disabled. Sorry. Apparently by using Typekey authentication for comments, I’m able to bypass the error. Will have a look at the in-built authentication routines of the script to see if I can identify what’s causing the original error.
Sorry for the inconvenience but I guess folks who want to comment will have to utilise the Typekey authentication service until I can work out the bug.
