badly signed gpg mail just gives an oops

[Martin Pool]

I was accidentally sending GPG mails to malone that weren't properly ascii armored therefore were seen as invalidly signed when received by Launchpad. However, the rejection message it sends back to me gives no clue that this is what the problem is, just an oops that makes it seem more like a transient error in Launchpad:

----
An error occurred while processing a mail you sent to Launchpad's email
interface.

Error message:

Sorry, something went wrong when Launchpad tried processing your mail.
We've recorded what happened, and we'll fix it as soon as possible.
Apologies for the inconvenience.

If this is blocking your work, please file a question at
https://answers.edge.launchpad.net/launchpad/+addquestion
and include the error ID OOPS-1229CEMAIL3 in the description.

----

The OOPS has

Traceback

  InvalidSignature: Signature couldn't be verified: (7, 8, 'Bad signature')

    Traceback (most recent call last):
  Module canonical.launchpad.mail.incoming, line 249, in handleMail
    principal = authenticateEmail(mail)
  Module canonical.launchpad.mail.incoming, line 104, in authenticateEmail
    raise InvalidSignature("Signature couldn't be verified: %s" % str(e))
InvalidSignature: Signature couldn't be verified: (7, 8, 'Bad signature')

Maybe you could just give that message back in the rejection.