Technical Data 

Supported address types

Address type in SAP Exchange Connector	Corresponding address type in SAP system	Meaning
SMTP	INT	Internet mail
X400	X40	X.400 mail
Configurable	FAX	Fax number

The address types SMTP and X.400 are fixed, because they are based on Microsoft standard values. Enter the value of your fax connector in the Exchange System Manager for the fax address type.

Transport of message notifications and status notifications

The table below shows message notifications and status notifications depending on the type of Exchange connection (direct or via a backbone) and the address type of the SAP Exchange Connector/the backbone type.

Not- ifica- tion type	Exchange « SAP coupling		Exchange « backbone « SAP coupling
	SMTP	X.400	ESMTP	SMTP	X.400 1988 * normal mode
IPM	X	X	X	X1	X
DR	X 3	X 3	X 3	X1	X3
NDR short	X 3	X 3	X 3	X1	X3
NDR long	X 3	X 3	X 3	X1	X3
RN	X 3	X 3	X 4	¾	X3
NRN	X2 3	X2 3	X2 4	¾	X2

Abbreviations:

IPM      Interpersonal mail (e-mail)

DR       Delivery receipt

NDR     Non-delivery receipt

RN       Read notification          

NRN     Non-read notification

X          Notification type transferred correctly with all necessary information

¾        Notification type not supported by the SAP system for this protocol

1          Notification type supported only as a message, not as a report

2          Notification type supported only from Exchange to SAP

3          Only possible with Exchange 2000 Service Pack 2 upwards, since these versions include a Microsoft hot fix to resolve the message ID problem (SRZ010716000612).

4          Not possible yet because of a Microsoft error not corrected by Exchange 2000 Service Pack 2.

*           X.400 conformance = 1988 normal mode, Allow Exchange Content option = No in the X.400 connector settings

Notes:

·         “Backbone” is the configuration with which two SAP systems are coupled using two Exchange servers. This is not possible for the fax service. Whether DR and NDR are supported for a fax connector connection depends on the fax connector manufacturer.

·         For the address type SMTP, note that if the recipient is on the local Exchange server, no special settings are required to enable receipt of status notifications.

Supported document formats

In the SAP Exchange Connector there is no restriction on the data to be transported. Because of possible character set differences in the SAP system and the SAP Exchange Connector, a character set conversion is performed in the RFC layer. This conversion applies to the following formats:

·         RAW (corresponds to basic document in Exchange)

·         TXT (Notepad text)

·         LOG (SAP Exchange Connector log files)

·         R3F (SAPforms attachments)

If you use other text attachments that are to be subject to character set conversion, specify these in the Exchange System Manager when configuring the Gateway service. Attachments sent from the SAP system are always converted into NT Unicode, while those sent to the SAP system are converted into the SAP code page set there.

If RAW attachments are to be transported via the Internet, you must configure this in the Exchange System Manager. Choose Global Settings in the console tree. Select Internet Message Formats, and invoke the context menu. Choose Properties. On the General tab page, choose Add…. Select the type text/plain and enter the associated extension RAW.

The SAP Exchange Connector does not support the transport of OLE objects, references, and messages within messages. Since SAP Exchange Connector 2.0 passes text data to Exchange in Unicode, as version 1.54 did, and Exchange (SP 1) always encodes this data in UTF‑8, the recipients should use a UTF-8-compatible mail program, such as Outlook 2000 or Outlook Express.

Restrictions

1.       In the case of X.400 data traffic via a backbone infrastructure, the recipient address for (N)DR and the sender address for IPM are not returned in X.400 format, but as a distinguished name, if the Exchange servers involved are operated without directory synchronization.

2.       The SAP-specific attributes in the Queue Out and Queue In folders cannot be accessed with Outlook. (The attributes are described as “named properties” in Outlook.)

3.       If an X.400 address contains DDA address components, Exchange does not take these into account for deliveries to mailboxes.

4.       Before operating the SAP Exchange Connector, read the current notes for the components BC-SRV-COM and BC-SRV-COM-MSX in SAPNet.

5.       Moving an SAP Exchange Connector from one routing group to another is not supported.