Tony Garnock-Jones writes: > OK, that's good; it doesn't explain Lionel's report that SENDing with > "message-id" set led to a correspondingly-set "message-id" on the resulting > MESSAGE, though. FWIW, my user-supplied message-id got prepended. The received MESSAGE frame contained two message-id headers. Cheers, Lionel