Yes, this is one thing to watch out for. If the spamtrap accounts include some accounts that *were* previously active as user accounts, you *really* need to monitor those for the occasional ham slipping in.
I agree wholeheartedly.. This is also a concern for corpus maintainers for SA too... Corpus pollution hurts us all (especially the opposite case where spam ends up in the ham corpus.. very deadly to the SA scores)
As for that kind of spamtrap, I don't use that type of account myself. Too many problems.. I use hand "seeded" addresses, obviously bogus addresses I've purposely mentioned in technical examples on mailing lists with web archives, etc.
Things like: [EMAIL PROTECTED]
Which I might use in an example of a cronjob that checks system status and emails it to my pager.. Usually takes 1-4 weeks for some spammer to mine it off the web archives and start using it...
