This article was previously published under Q173326
This article has been archived. It is offered "as is" and will no longer be updated.
Microsoft Message Queue Server (MSMQ) 1.0 Explorer shows encrypted messages asclear text in the destination queue. This behavior is by design. You candetermine from the Explorer or from inside an application if a specificmessage was encrypted when it was sent.
MSMQ provides a secured channel for sending private, encrypted messagesthroughout your MSMQ enterprise. MSMQ ensures that the body of privatemessages are kept encrypted from the moment they leave the source QueueManager to the moment they reach their target Queue Manager.
Messages are encrypted at the source computer and decrypted at thedestination computer. With encryption and decryption provided by MSMQ QueueManagers, applications do not have to encrypt messages when they are sentor decrypt messages when they are received. They appear in the destinationqueue as clear text for the receiving application to read.
The privacy level of a queue (PROPID_Q_PRIV_LEVEL) determines how the queuehandles encrypted messages. If a queue's privacy level is Optional(MQ_PRIV_LEVEL_OPTIONAL), a user can verify whether a message sent to thequeue was encrypted or decrypted by checking the messages properties inMSMQ Explorer. Take a look at the Sender tab in message properties in theExplorer to find if it was encrypted or not.
You can pass PROPID_M_PRIV_LEVEL to MQReceiveMessage and look at thereturned value to find out if a message was sent encrypted.
For more details on privacy issues and complete examples of sending aprivate message using C API and ActiveX, take a look at "Private Messages"topic in SDK Online help.