Byte Order Mark (BOM) in BizTalk message

I was sending out some eRx files to a folder to use to validate with the NIST validation tool. When we tried to import the message to the tool, it failed with an invalid xml error and was showing a 'special' character at the beginning of the file. Turns out, the send port was appending a Byte Order Mark (BOM). The following blog post describes the issue in better detail. A big question I need to dig into more, is why a pass-through pipeline was appending a BOM? Solution was to change the pipeline to xml transmit and set PreserveBOM to false.


http://mindovermessaging.com/2013/08/06/removing-the-bom-from-outgoing-biztalk-files/