Show TOC

Configuring the Receiver Mail AdapterLocate this document in the navigation structure


You configure the receiver mail adapter to convert XI messages to e-mails.

  1. Select the Transport Protocol:
    • SMTP

      You use SMTP (Simple Mail Transfer Protocol) to transfer e-mails to an e-mail server.

    • IMAP4

      You use IMAP4 (Internet Message Access Protocol) to put e-mails in a folder of an e-mail server.

  2. Select the Message Protocol:
    • XIALL

      All information of the XI message is put in the message text of the e-mail. The content of the XI message is the same as the content of the RFC822 mail message.


      The payload of the XI message is used to create the mail message.

      If the payload is in mail package format, the header information is also used for the e-mail.

      If mail package format is not used, the header information is obtained from the adapter configuration described below.

  3. Select the Adapter Engine on the Integration Server, or select a non-centrally installed Adapter Engine.

    This selection is not available in the PCK.

Define Connection Parameters for the Mail Server

  1. Under URL, enter the address of the e-mail server:
    • For SMTP: smtp://mailserver, for example
    • For IMAP: imap://imapserver/XIOutBox, for example
  2. If the server expects authentication, select Configure User Authentication.
    • Choose the Authentication Method.
      • Plain
      • CRAM-MD5
    • Enter the User Name and Password, and confirm.
  3. If you have selected SMTP as the transport protocol, you have the option to Send Delivery Status Notification.

    Under To, enter the e-mail address of the receiver of the delivery status notification.

Define Mail Attributes

  1. If you have selected XIPAYLOAD as the message protocol and the XI payload is a mail package document, you can select Use Mail Package.

    For the format, see Example below.

    If the XI payload is not a mail package document, make the entries for mail attributes.

  2. Enter the mail attributes:
    • From: E-mail address that message comes from
    • To: E-mail address that message is sent to

      If you enter more than one address, separate them with a semicolon.

      If you have specified an IMAP server under URL, the message is saved in the specified folder but is not sent to the receiver specified under To.

    • Cc: Additional e-mail addresses that e-mail is to be sent to.

      These addresses are visible to the receiver.

    • Bcc: Additional e-mail addresses that e-mail is to be sent to.

      These addresses are not visible to the receiver.

    • Enter the Subject of the e-mail message.
  3. If you want to encode the content of the e-mail message, select Content Encoding.
    • None
    • base64
    • quoted-printable
  4. If you have selected XIPAYLOAD as the message protocol and you want to forward XI attachments in the e-mail attachments, select Keep Attachments.

    You use the PayloadSwapBean module to swap the application payload with one of the attachments.

    More information: PayloadSwapBean

Define Security Parameters for Message Protocol XIPAYLOAD

  1. If you want to encrypt e-mails and give them a digital signature in the corresponding receiver agreement in the Integration Server or in the PCK, select S/MIME.

    To do this, you must have set the Keep Attachmentsindicator.

    More information: SAP NetWeaver Library under Function-Oriented View → Process Integration → Integration Directory → Defining Receiver Agreements → Security Settings for the Receiver Mail Adapter

    • Specify the Persist Duration in days, hours, minutes, and seconds.

      This specification is not currently used, but will be used in the future for security archiving.

Define Adapter-Specific Message Attributes

  1. Select the Advanced  tab page.
  2. To save adapter-specific attributes in the message header of the XI message, select Use Adapter-Specific Message Attributes and Variable Transport Binding.

    The following attributes in the message header are then available for processing:

    • User: (technical name: TServerLocation )
    • Authentication key: (technical name: TAuthKey )

    The following mail header fields are available for processing:

    • From: (technical name: THeaderFROM )
    • To: (technical name: THeaderTO )
    • Cc: (technical name: THeaderCC )
    • Bcc: (technical name: THeaderBCC )
    • Subject: (technical name: THeaderSUBJECT )
    • Reference to the mail that is to be replied to: (technical name: THeaderIN-REPLY-TO )
    • Reply to: (technical name: THeaderREPLY-TO )
    • Mail client program: (technical name: THeaderX-MAILER )
    • Send confirmation of receipt: (technical name: THeaderDISPOSITION-NOTIFICATION-TO )
    • Priority: (technical name: THeaderPRIORITY )
    • Importance of message: (technical name: THeaderIMPORTANCE )
  3. To transfer further header fields, set the relevant indicator for Variable Header. The technical names for the fields are XHeaderName1 , XHeaderName2 , and XHeaderName3 .

    The parameters are included in the mail header under the names specified here.

    The attribute namespace for the adapter is

Display and Define Authentication Keys}

  1. If authentication is required for the receiver system, you can enter a password with confirmation for each key value. This means that you do not need to write passwords in the enhanced message header.
    • If you want to enter or display the respective authentication key, select View Authorization Keys.
    • You can enter and confirm passwords for each authentication key value (TAuthKey).

Define the Adapter Status

  1. Set the adapter to Active to enable messages to be exchanged.

Define Parameters in Advanced Mode

  1. To specify additional parameters for the adapter configuration, select Advanced Mode.

    Enter additional parameter names and parameter values in the table.


XI payload with mail package:

<?xml version="1.0" encoding="UTF-8"?>
<ns:Mail xmlns:ns="">
  <Reply_To />
This is the content.