oops when responding to merge proposal review via email

Downloading the email message and running GPG on it says that there is a CRC error.

So this looks like an encoding problem on the client side.

(Downloading the email from the librarian using the OOPS reference.)

That's surprising because I use the same client to respond to merge proposals as I do to respond to normal emails and I've never had a problem with it. I suspect that something's reformatting or otherwise transforming the message from the time the mp mta receives it to the time it's put into the librarian.

On Thu, Jan 22, 2009 at 03:16:00PM -0000, Francis J. Lacoste wrote:
> Downloading the email message and running GPG on it says that there is a
> CRC error.
>
> So this looks like an encoding problem on the client side.

I came to the same conclusion first, after doing the same thing you did,
but then I opened the downloaded mail in mutt, which managed to verify
the signature (using gpg).

We already do some decoding and normalization before sending the text to
gpg. My guess is that there's some other decoding or normalization we
need to do as well. Looking at the source code for mutt would be a
start.

OOPS-1140CEMAIL1

I got OOPS-1144CEMAIL9 when sending a signed email as a response to a merge proposal. The error is 'Bad Signature' but the downloaded email verifies. Sent from mail.app.

We have recently complaints about this Bad Signature OOPS, as OOPS-1150CEMAIL3 shows, and as jml pointed through https://answers.edge.launchpad.net/launchpad/+question/62796. What else can be done for this one to be investigated?