Ben,
I've had exactly the same here today, I'm not 100% sure how I fixed it, but fix it I did.
I spotted the mime browser cache service was dead, restarted it and it died again.
I ran omtidyallu -M for about two seconds, realised how log it might take and killed it.
I restarted the browser cache (omon mime) again and it seemed to fix it.
What or how this worked who knows, it's got about 40 people off my back this morning though.
It seems strange that these errors seem to appear at around the same time to various people, is there a new form of spam message that is killing the service somehow?
I've no idea how to find that out though, just a thought.
Phill

