occasional corruption of signed messages

This mail got corrupted by the list. The list archives have it as https://lists.launchpad.net/subunit-dev/msg00008.html.

This is the copy I received back from the list.

Soory you are at the wrong email and person Idon't why I'm not a
professionnel in fixing and reapirind Bugs in Ubuntu I wish you find a
solution good luck.

Soory you are at the wrong email and person Idon't why I'm not a
professionnel in fixing and reapirind Bugs in Ubuntu I wish you find a
solution good luck.

Barry. Can you triage this? what will it take to fix if it is a problem?

This will take some investigation and analysis of the good and corrupt messages, and an analysis of the paths this message may have taken through the mailing list. A few hours to determine the cause. I can't estimate what it would take to fix. It could be an upstream bug.

Barry, attached is a unified diff between the good and bad messages.

Hi Barry, Robert.

We don't seem to have made any progress in triaging this bug. I feel that corrupting signed messages warrant a high priority for fixing, but we do not have enough information to start coding. Was my diff helpful? Are there any new ideas about the cause of this? client, relay path, content that causes a reflow of text?

On Sat, 2009-07-04 at 15:11 +0000, Curtis Hovey wrote:
> Hi Barry, Robert.
>
> We don't seem to have made any progress in triaging this bug. I feel
> that corrupting signed messages warrant a high priority for fixing, but
> we do not have enough information to start coding. Was my diff helpful?
> Are there any new ideas about the cause of this? client, relay path,
> content that causes a reflow of text?

I haven't looked at the diff; however as its is reproducible for me,
perhaps something useful you could do is to reproduce it yourself:
send a signed mail to a lp list. Check it validates (it should). Forward
the mail like I did, signing the forward too. Check it fails to
validate.

That would rule out most of my mail-path.

-Rob

I've verified this using the recipe you provided in your previous comment. I've also verified this using a stock Mailman 2.1.9 installation, so I believe it is a bug in Mailman. Launchpad uses the latest stable MM release (2.1.12) so I will try updating my test instance and see if the bug still exists, though I suspect it will.

There's definitely something client-dependent here. First, the forward should be as an attachment, however Claws (Linux) and Mail.app (OS X) seem to handle attachments differently because while they both fail, they fail in different ways. The Claws failure is closer to what I think you might see. I think Mailman is messing up the MIME structure of the message, and possibly breaking headers in the wrong place.

Launchpad's implementation of mailing lists isn't to blame here.