Previous Topic: X-header RequirementsNext Topic: Document Classifications


X-header Limitation in Exchange 2003

Problems in Exchange 2003 cause the following x-header limitation for outgoing emails processed by a CA DataMinder Outlook endpoint agent and subsequently sent using Exchange.

Do not include periods in x-header names

If your x-header name includes a period character (such as X—Case.ID), Exchange 2003 will fail to insert the x-header into the email. In detail, although the Outlook endpoint agent successfully sets the appropriate email property, Exchange 2003 subsequently fails to convert this property to an x-header when this email is sent as an Internet Mail.

Note: This limitation has been fixed in Exchange 2007. Likewise, this limitation only applies to outgoing emails processed by the Outlook endpoint agent; it does not apply to emails processed by CA DataMinder Exchange or Domino server agents or the Notes endpoint agent.

More information:

X-Headers and Smart Tags

X-header Requirements