GA Spam protection, processing steps triggered by spam submissions

Hi All,

a Spam attack has been received on our Eloqua instance.

Even though the spam attack has been recognized, and then the spam submissions have been identifitied and stored as spam, all the processing steps (like sending notification email) involved in the form attacked has been triggered by each of the spam submission, leading to massive notifications.

So my question is the following, is this the way this feature supposed to work or the configuration is not properly set? Eventually exists any workaround available to mitigate this behavior?

Thanks

Luca