Comment 4 for bug 68014

Please, would you add concrete links and references to concrete messages that got this behaviour so I can concentrate exactly with the broken messages?

I was planning to add some extra internal logging to track this kind of changes, in the mean time, I need to figure it based on what I see in our database so it's easy if I know exactly a set of messages that have this problem.