Sender and receiver determination

The following outlines the order in which Interchange determines sender and receiver. This information is provided for users who may want to post messages to Interchange with their own tools.

Sender determination

  1. MIME headers are checked for X-Cyclone-From and X-Cyclone-To.
  2. Subject line
  3. To aid in true sender and true receiver determination, Interchange supports parsing the MIME subject line.The format of the subject line is compatible with Interchange 4.x.
  4. There are two valid formats
  5. truereceiver
    truereceiver; truesender
  6. We recommend the true receiver and true sender be simple alphanumeric strings without leading or embedded spaces. If spaces or non-alphanumeric characters are used, enclose the strings in quotes like so:
  7. 'true receiver';'true sender'
  8. Although supported, non-alphanumeric characters in the strings is not a best practice.
  9. A message ID MIME header formatted in the style of Interchange 4.x.
  10. From header. The From header is typically an email address. Interchange tries to match the contents of the From header with a configured routing ID. So Interchange may need to be configured to have a routing ID that is really an email address.
  11. Payload parsing. This is not supported for signed and encrypted documents.
  12. Exchange points assigned to specific parties. Signed and encrypted messages are not supported.

Receiver determination

  1. MIME headers are checked for X-Cyclone-From and X-Cyclone-To. This is not supported by Interchange 4.2 or Cyclone Central.
  2. Subject line.
  3. Pickup exchange point .
  4. Payload parsing. This is not supported for signed and encrypted documents.
  5. Exchange points assigned to specific parties. Signed and encrypted messages are not supported.

Related topics

Related Links