just an idea:
once there's broad consensus about what certainly is *not* a valid bugtracker, could the package interface check that, too? the way it already detects missing bug tracker links?

you certainly cannot make the machine read the wiki and check if all criteria are met... but there could be something like a blacklist based on either regular expressions or a simple string comparison.

think of the following situation: a devoloper puts package A, version 0.1 in -testing. bugtracker: talk maemo.org. - it's soon clear that talk.maemo.org is not a valid bugtracker (a specific thread might be, don't know), so there's a few thumbs down from people who know the rules. but there's also thumbs up rom those who don't care and simply think the application is cool.

a week later, the same developer puts version 0.2 in testing, along with a new package B. again, all bug tracker fields contain only talk.maemo.org. - what will happen is a race between those voting up and those voting down.... and some version may still escape to extras.

putting talk.maemo.org on the blacklist as soon as it's first seen could prevent this and wouldn't require attention of the testers wrt subsequent packages.