Merge-proposal reply truncated

I think its most likely that your mailserver didn't send all the mail; can you exclude that possibility?

Looking at the examples in this bug and the duplicates it becomes obvious that a single dot on a line is the culprit. That is the international sign among mail servers for EOT. These dots end up there because of wrapping, so this is probably related to bug 724864. I'll see if I can tackle that one, too.

OK, I have tried to trigger this using the local directory delivery and I even set up a POP3 server to test the POP3 pick up method. The latter is what I believe is used in production. No line wrapping or truncating occurs so it looks like this is happening before the mail arrives at the LP mailbox.

I guess the admins should look into this to see where in the MTA stack this might happen. I still think it is a combination of line wrapping and SMTP/sendmail interpreting lonely dots as EOT.

Filed rt #45740 in queue launchpad.

IS says this has been fixed. Can somebody please try to verify that?

Quoting from the RT:

This seems to have been a combination of message encoding, some slightly
odd methods of mail rewrites and bad luck.

The messages are being wrapped to 76 characters per line because the
message is encoded as "quoted-printable". Unfortunately, the mail
pipeline on mx.launchpad.net was acting strictly and using the leading
period as EOT (as you surmised).

I have turned this strict behaviour off and sent a few test messages to
ensure that it works as expected.

Please let me know if this does not solve your problem or if you have
any further questions?

This works fine now.