I would guess it's some kind of internal error, seeing as the incriminating content is powered by Posterous itself...