Comment 24 suggests to me that this bug should be closed (?). Because it seems to eliminate the possibility of the message appearing with (0x0f).
Comment 24 suggests to me that this bug should be closed (?). Because it seems to eliminate the possibility of the message appearing with (0x0f).