Orphaned part detection issue.

While checking a user bug report, I've discovered something really worrying that may lead to data (i.e. message) loss. The actual cause of this problem has not (yet) been identified, but since data loss was observed, a formal warning is in order:

An implementation of an orphaned callback notification with code to delete the orphaned part reported, either explicitly or by returning TRUE from the notification method, may wipe out other normal (i.e. non-orphaned) messages.

I've observed this a couple of times without being able to trace down the reason.

In case you have implemented the orphaned part notification method, you are advised to remove the callback handler ASAP.

You can follow the progress on this issue on the relevant Issue Tracker Ticket. More information will also be posted on the blog.