BTW the idea of USER_IN_BLACKLIST being ignored for bayes is so that if a user screws up and accidentally BLs a ham source, it won't pollute Bayes as well.
I think in 3.0.0 we've added more logic so that it won't be learned *at all* in that situation -- not as ham or spam.
Justin, by the virtue of the ALL_TRUSTED test being matched, one can infer that the user is using some form of 3.0 prerelease code, although not necessarily which release.
Also, looking at SA 3.0 RC3's PerMsgStatus.pm I don't see code to prevent learning of an email if it's blacklisted.
It's considerably changed from 3.0-pre4, but it does neither appear to have any added criteria to not autolearn black/whitelisted emails.
