Mitigating Email Spam in Bug Report Frontend

I developed a game bug reporter where, if HTTP fails, users email a JSON report. How can I stop spam, for example:

def push_record(entry):
    # simulate sending a bug email
    pass

hey, u can add a simple captcha/honeypot and rate limit ip addresses. that reduces spm. i used these ideas incase my email server gets spammed before sending bug reports. not foolproof, but works good.

hey owen, u ever try a verification email step? it sends a one-time link to confirm bug reports. might be a neat way to avoid faked spam. has any1 else used this method or found an interesting twist on it?

A further idea to address spam without overcomplicating the user experience is to introduce a backend verification mechanism that uses a digital signature in the bug reports. By generating a signature when the reporter is instantiated in the game, it is harder for repeated emails to be sent from unauthorized sources. This tactic can be combined with lightweight client-side checks, such as a small delay or hidden field that is only submitted by genuine users. In practice, this provides an additional layer of protection without impacting valid reports.