-The following values may be passed back in the *state* field
-of the returned message buffer.
-
-
- .. list-table::
- :widths: auto
- :header-rows: 0
- :class: borderless
-
- * - **RMR_ERR_BADARG**
- -
- The message buffer pointer did not refer to a valid message.
-
- * - **RMR_ERR_NOHDR**
- -
- The header in the message buffer was not valid or corrupted.
-
- * - **RMR_ERR_NOENDPT**
- -
- The message type in the message buffer did not map to a known
- endpoint.
-
- * - **RMR_ERR_SENDFAILED**
- -
- The send failed; ``errno`` has the possible reason.
-
-
-
-The following values may be assigned to ``errno`` on failure.
-
- .. list-table::
- :widths: auto
- :header-rows: 0
- :class: borderless
-
- * - **INVAL**
- -
- Parameter(s) passed to the function were not valid, or the
- underlying message processing environment was unable to
- interpret the message.
-
- * - **ENOKEY**
- -
- The header information in the message buffer was invalid.
-
- * - **ENXIO**
- -
- No known endpoint for the message could be found.
-
- * - **EMSGSIZE**
- -
- The underlying transport refused to accept the message
- because of a size value issue (message was not attempted to
- be sent).
-
- * - **EFAULT**
- -
- The message referenced by the message buffer is corrupt (nil
- pointer or bad internal length).
-
- * - **EBADF**
- -
- Internal RMR error; information provided to the message
- transport environment was not valid.
-
- * - **ENOTSUP**
- -
- Sending was not supported by the underlying message
- transport.
-
- * - **EFSM**
- -
- The device is not in a state that can accept the message.
-
- * - **EAGAIN**
- -
- The device is not able to accept a message for sending. The
- user application should attempt to resend.
-
- * - **EINTR**
- -
- The operation was interrupted by delivery of a signal before
- the message was sent.
-
- * - **ETIMEDOUT**
- -
- The underlying message environment timed out during the send
- process.
-
- * - **ETERM**
- -
- The underlying message environment is in a shutdown state.
-
-
+The following values may be passed back in the *state* field
+of the returned message buffer.
+
+
+ .. list-table::
+ :widths: auto
+ :header-rows: 0
+ :class: borderless
+
+ * - **RMR_ERR_BADARG**
+ -
+ The message buffer pointer did not refer to a valid message.
+
+ * - **RMR_ERR_NOHDR**
+ -
+ The header in the message buffer was not valid or corrupted.
+
+ * - **RMR_ERR_NOENDPT**
+ -
+ The message type in the message buffer did not map to a known
+ endpoint.
+
+ * - **RMR_ERR_SENDFAILED**
+ -
+ The send failed; ``errno`` has the possible reason.
+
+
+
+The following values may be assigned to ``errno`` on failure.
+
+ .. list-table::
+ :widths: auto
+ :header-rows: 0
+ :class: borderless
+
+ * - **INVAL**
+ -
+ Parameter(s) passed to the function were not valid, or the
+ underlying message processing environment was unable to
+ interpret the message.
+
+ * - **ENOKEY**
+ -
+ The header information in the message buffer was invalid.
+
+ * - **ENXIO**
+ -
+ No known endpoint for the message could be found.
+
+ * - **EMSGSIZE**
+ -
+ The underlying transport refused to accept the message
+ because of a size value issue (message was not attempted to
+ be sent).
+
+ * - **EFAULT**
+ -
+ The message referenced by the message buffer is corrupt (nil
+ pointer or bad internal length).
+
+ * - **EBADF**
+ -
+ Internal RMR error; information provided to the message
+ transport environment was not valid.
+
+ * - **ENOTSUP**
+ -
+ Sending was not supported by the underlying message
+ transport.
+
+ * - **EFSM**
+ -
+ The device is not in a state that can accept the message.
+
+ * - **EAGAIN**
+ -
+ The device is not able to accept a message for sending. The
+ user application should attempt to resend.
+
+ * - **EINTR**
+ -
+ The operation was interrupted by delivery of a signal before
+ the message was sent.
+
+ * - **ETIMEDOUT**
+ -
+ The underlying message environment timed out during the send
+ process.
+
+ * - **ETERM**
+ -
+ The underlying message environment is in a shutdown state.
+
+