Configuring the Sender Mail Adapter 

Use

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

Procedure

...

       1.      Select the Transport Protocol:

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

○       You use POP3 (Post Office Protocol Version 3) to retrieve e-mails from an e-mail server.

       2.      Select the Message Protocol:

○       XIALL

The content of the RFC822 e-mail matches the content of the XI message. The XI message is a multipart MIME message with a SOAP envelope as its first part.

More information: Messages, under XI Message Protocol.

○       XIPAYLOAD

The content of the e-mail is put in the payload of the XI message.

If you do not select Use Mail Package, the information about the sender (From), receiver (To), Cc, and Subject of the e-mail is lost.

       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

       4.      Under URL, enter the address of the mail server:

For example: imap://imapserver/XIInBox

       5.      If the server requires authentication, select Configure User Authentication.

○       Select the Authentication Method:

■       Plain

■       CRAM-MD5

○       Specify the User and Password for accessing the server, and confirm.

       6.      Under Poll Interval (min), specify the time interval after which e-mails are to be called on the server.

       7.      If you have selected IMAP4 as the transport protocol, you can delete messages on the e-mail server after reading.

○       Select Delete Messages After Reading.

○       Specify a Folder for Deleted Messages on the server.

       8.      If you want to generate a report for every adapter poll procedure, select Generate Fetch Report.

An XI message with the following information is generated:

○       Interface namespace: http://sap.com/xi/XI/Mail/30

○       Interface Name: FetchReport

Define Further Parameters for Message Protocol XIPAYLOAD

       9.      If you have selected XIPAYLOAD as the message protocol, you make additional entries in the adapter configuration.

More information: Defining Parameters for Message Protocol XIPAYLOAD

Define Adapter-Specific Message Attributes

   10.      Select the Advanced tab page.

   11.      To save adapter-specific attributes in the message header of the XI message, select Use Adapter-Specific Message Attributes.

The following mail header fields are added to the XI message header if the sender can make them available, and if you have selected Variable Transport Binding.

○       Mail account user: (technical name: SUser)

○       From: (technical name: SHeaderFROM)

○       To: (technical name: SHeaderTO)

○       Cc: (technical name: SHeaderCC)

○       Subject: (technical name: SHeaderSUBJECT)

○       Reference to the mail that this mail is replying to: (technical name: SHeaderIN-REPLY-TO)

○       Address to which reply is to be sent: (technical name: SHeader-REPLY-TO)

○       Mail client program: (technical name: SHeaderX-MAILER)

○       Send confirmation of receipt: (technical name: SHeaderDISPOSITION-NOTIFICATION-TO)

○       Priority: (technical name: SHeaderPRIORITY)

○       Importance of message: (technical name: SHeaderIMPORTANCE)

   12.      To transfer further header fields, set the relevant indicator.

You can save Variable Headers and their values in the XI message header.

The technical names are XHeaderName1, XHeaderName2, and XHeaderName3.

The attribute namespace for the adapter is http://sap.com/xi/XI/System/Mail.

Define the Adapter Status

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

Define Parameters in Advanced Mode

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

○       Specify the additional parameter names and parameter values in the table:

○       For the security settings, enter values for the receiver party and receiver communication component (parameters: XI.ReceiverParty, XI.ReceiverService).

○       If you set the parameter IMail.AssumeXMLContent = true in the table, the text of the message is interpreted as XML and included unchanged in the mail package.

If you do not set this parameter, the information is taken from the content type of the MIME header.

If the type there is application/xml or text/xml, the text of the message is copied as XML; otherwise it is copied as text.