> The SpamFilter does not stash anything in the Session (because spambots > sometimes do not send cookies).
D'oh, shouldn't have written this before breakfast. Of course we write the hashfield name in the Session. But my comment still stands not wanting to do this in a Stripes-dependent manner. I especially don't want us rejecting edits in multiple places. Besides, I want to enhance SpamFilter to go into a direction of SpamAssassin, that is, allow different weights for different tests. This means that SpamFilter must get all the relevant data and be able to reject/approve things without the framework getting in the way. /Janne
