More robust logic for tree message forward

Handle situation where a receiving/forwarding host can't unpack the header
of the sender (not compatible version).