The anti-spam bot is not static. It has to be constantly updated, to keep up with constant activity by the producers of the many large splog farms that inhabit the blogosphere. It's going to produce false positives, as well as false negatives, and it's going to produce inconvenience to many bloggers.
This week, a recently applied update appears to have taken an excessive amount of innocent blogs with it. Major inconvenience to many. Can you say "egregious false positive rate"?
One blogger seems to have a way around the problem - at least to let your readers know what's going on.
If you still have access to your blog, you can still post a new widget at the top of your blog that contains text to tell your readers what has happened.
Using Page Elements, create a text widget with a brief message, and position the widget in a conspicuous place on the blog.
Note to Readers - Blogger's spam robot has run amok and has tagged 1000s of blogs, including this one, as "spam." Obviously, I am not a spam blog.
So, if you can't post but you can access the Layout wizard, you can at least let your readers know why you aren't posting.
As far as resolving this for your blog, I'm sure that you have done what a few other bloggers have instinctively done, and started the well known blog review request process.
In this case, and based upon the level of complaints seen so far, I suspect that's going to be a waste of time from you. Unless Blogger brings in extra staff, there's no way that they can review all of the requests generated by this experience. How long does a review requests typically take? Multiply that by 100 (minimum). Would you really want to wait that long?
> > (Update 17:00): Blogger admits to the problem, and implies that they are resolving it on their own.