Over the last few weeks we have been working on backporting security fixes from the GForge project. It is not an easy job, and Luke Hudson (our appointed security guy) has been doing great. We silently deployed an update last week that closed the gaps, and went mostly flawlessly. 
(If you are having trouble with Eduforge, it may be a side-effect of our changes -- let us know via the Eduforge Help forum and we'll jump onto it) .
... and just as we were testing an update to the blogging facility to stop spam... some crazy spammer hit us in full force trying hard to get some nasty stuff to be posted in the trackbacks. As in, thousand of attemps per minute. Nothing got posted in the blogs, but people who have been blogging on Eduforge got a bit hit of spam messages. Yuck 
We blocked trackbacks within minutes of the spam run starting, so it's been stopped. We will reenable trackbacks once the new code is in place and things are safe. I don't want to risk another run like this.
We are very sorry this has hit our users -- and we keep on fighting the spam wars, whether we like it or not.
