Fixed issue where eventual send wasn't parsed correctly
Fixed issue where eventual send wasn't parsed correctly

Make sure we don't drop the correct evenutalSend bit, in case binaryConsecutiveMessage doesn't do anything.

Signed-off-by: Stefan Marr <46f1a0bd5592a2f9244ca321b129902a06b53e03@stefan-marr.de>

richard-roberts/SOMns,smarr/SOMns,smarr/SOMns,smarr/SOMns,smarr/SOMns,VAISHALI-DHANOA/SOMns,richard-roberts/SOMns,richard-roberts/SOMns,richard-roberts/SOMns,smarr/SOMns,richard-roberts/SOMns,richard-roberts/SOMns,MetaConc/SOMns,MetaConc/SOMns,VAISHALI-DHANOA/SOMns,smarr/SOMns,richard-roberts/SOMns,smarr/SOMns,VAISHALI-DHANOA/SOMns,MetaConc/SOMns