Announcing bug tracker

[Bill Hacker]

Oliver Fromme wrote:

*snip*

There's just one small problem.  It seems that the bug
tracker simply uses the user-part of the email address
as account name.  However, my client on this machine
generates unique hashes when sending articles to public
newsgroups, in order to protect 
against?

spam.  For example, this
posting comes from:  check+j2e0vn00rsh5xb2o at xxxxxxxxxx
One of the postings I made to the bugs list 3 months ago
made it into your tracker with the this account name:
check+ixjt6r00rst8bncd
Obviously that makes it somewhat difficult to handle,
because a different hash is generated each time.  Also,
it's not possible to reply to such an address when it
is older than two weeks ...  After two weeks, any reply
is automatically answered with a "fresh" email address
(I've currently disabled that feature, though, so I could
get a possword for my account).
Unfortunately, I don't know how to easily solve that
problem.
Best regards
   Oliver
Dunno how that would block spam that you cannot block just as effectively by 
other means.  Ones that do not break *anything*.

In fact, you may be creating more server workload in general for legitimate 
callers, not to mention possible collateral spam damage.

Which of us is out of step here?

Bill