How are users addressed in the mail system group?
If a mail system group user has an SAP user, this user can be selected as the recipient. If a mail system group user does not have an SAP user, their Internet mail address can be entered directly on the send screen or they can be selected from an LDAP service. The external mail system appears as the LDAP server.
How are messages sent internally in the SAP System to an SAP user(case 1)?
The message is forwarded using the communication method Internet mail to the mailbox in the external mail system (the home address of the user). The standard address that has been specified for the communication method Internet mail for the user who sent the message is used as the sender address. In our example, it is in the form <user>@SAP.company.com.
How are messages sent externally from the SAP System to an address outside the mail system group (case 2)?
The sender address is also the standard address of the user who is sending the mail, therefore it is in the form <user>@SAP.company.com. This address is converted into the form <user>@company.com by an alias file. The conversion can take place, for example, in one of the MTAs between the external mail system and the firewall.
Where do replies to messages sent from the SAP System go?
Since the reply-to-address is not entered, the reply is sent to the sender address. Two cases can be differentiated:
Case 1 - Internal sending (Message: SAP ® Home mail system - Reply: Home mail system ® SAP ® Home mail system)
The sender address has not been converted and is in the form <user>@SAP.company.com. The reply created in the home mail system is sent to this address in the SAP System. As a result of the SAP user's address settings, the reply is forwarded to the user's home address, that is, it is sent back to the home mail system.
Case 2 - External sending (Message: SAP ® Home mail system ® External - Reply: External ® Home mail system)
The sender address has been converted and is in the form <user>@company.com. The reply from the external recipient (outside the mail system group) is therefore sent directly to the mailbox in the home mail system.
Where are statuses of messages sent from the SAP System returned?
The statuses up to the transfer of a message to the external mail system are always returned directly (synchronously) to the SAP System, irrespective of the sender address. The final statuses returned asynchronously (for example, the status Read) are sent to the sender address.
Case 1 - Internal sending (Message: SAP ® Home mail system - Status: Home mail system ® SAP)
Statuses returned asynchronously always go to the SAP System and can be accessed in the status history of the message sent. Senders also receive status information as a message in their home mail systems.
Case 2 - External sending (Message: SAP ® Home mail system ® External - Status: External ® Home mail system)
Statuses returned asynchronously are sent as a message to the mailbox in the sender's home mail system. The SAP System does not expect a status for recipients outside the mail system group domain. The transfer of the message to the connector for the external mail system is considered the final status (sent successfully).
Why is the home address not used as the user's standard address (and therefore as the sender address)?
If the home address is not used as the standard address, statuses of messages sent from the SAP System to mailboxes in the external mail system are returned to the SAP System. If you do not require status confirmation in the SAP System, you can use the address of the mailbox in the external mail system as both the standard address and the home address. In this case, the sender addresses do not have to be converted when messages are sent to recipients outside the mail system group. Furthermore, replies to messages from the SAP System are sent directly - that is, without first being sent to the SAP System (see above) - to mailboxes in the home mail system of the mail system group user.
What happens with executable documents?
External sending of executable documents is not currently supported. The executability is lost as soon as the document leaves the SAP System. A solution is planned.
Are all object types supported?
All object types are supported. SAPconnect provides conversion modules that convert SAP formats into standard formats, for example, SCR or OTF to PDF. The object types that are to be converted cannot be specified as supported formats for the node that represents the SAP Exchange Connector. For further information, see Formats.
Business objects sent from the SAP System can be converted into a URL, which recipients can use to access the objects. An Internet Transaction Server (ITS) with the data for the SAP GUI for HTML (webgui.car) is required for this.