2020-11-19 455140

455140 - Configuration of e-mail, fax, paging/SMS via

SMTP
Version 19 Type SAP Note
Language English Master Language German
Priority Recommendations / Additional Info Category Installation information
Release Status Released for Customer Released On 09.11.2015
Component BC-SRV-COM ( Communication Services: Mail, Fax, SMS, Telephony )

Please find the original document at https://launchpad.support.sap.com/#/notes/ 455140

Symptom

How do you configure e-mail, fax, paging or SMS in the SAP Web Application
Server using SMTP?
Which prerequisites and settings are required outside the SAP system?

Other Terms

INT, FAX, PAG, SAPconnect, SMTP

Reason and Prerequisites

Some information is missing.

Solution

General information, architecture, prerequisites, system environment

When e-mails are transferred using SMTP, the SAP Web Application Server
communicates directly with a mail server. No gateway or connector is necessary.
You can use any SMTP-compatible product as a mail server.
The SAP system always transfers the outbound mails to a single mail server. You
can set its host address and port number.
The SAP system can receive inbound mails from any number of mail servers. You
can reach each client using separate, configurable port numbers. You can address
the SAP system or its client most effectively by using an individual subdomain
for each client (for example, "crm-prod.company.com"). The assignment of these
subdomains to host name and port numbers of the SAP system is defined by the
routing rules on the mail servers.
As of Release 6.20, you can also send and receive fax and SMS or paging messages
using SMTP. These are packed in e-mails for this purpose. When sending, the mail
server uses the domain of the recipient addresses to send the e-mails to an
internal company fax or SMS server (for example "SMS=+491759628717@sms-
server.company.com"), or to an external provider (for example,
"[email protected]"). When receiving, the fax/SMS server or the
provider sends e-mails to addresses using the domain of the SAP system (for
example "[email protected]").

Security notes

Make sure that all of the mail servers that the SAP system communicates with
when receiving and sending messages have relevant virus scanners and spam
filters. We explicitly recommend protecting the receiving socket from the
outside by using the firewall to prevent direct delivery attempts by third

© 2020 SAP SE or an SAP affiliate company. All rights reserved 1 of 8

2020-11-19 455140

parties.
In addition, we recommend that the SAP system does not directly communicate with
a mail server outside the firewall.

Configuration

1. Profile parameter

To be able to use the SMTP functions, you must adjust the profile of
the SAP Web Application Server. We recommend that you activate SMTP on
all application servers of an SAP system. If this is not the case, the
SAPconnect send job may only be scheduled for servers on which SMTP is
active. The scheduling is then done by the standard job definition
(transaction SM36) rather than by the SAPconnect administration
(transaction SCOT, for a description, see 4.c).

For SMTP, you must set the profile parameters listed below. The placeholder
<*> stands for a number with which the parameters that can occur several
times are numbered sequentially, starting with 0.

a) icm/server_port_<*> = PROT=SMTP,PORT=<port>

This opens a TCP/IP port for receiving mails by the SMTP Plug-In.
<port> specifies the number of the port that you should use. This
must not be occupied by any other program on this host (for
example, Sendmail usually uses port 25). If no mails (including
status notifications) are to be received in this SAP system,
<port> can be set to 0.

You can use the TIMEOUT option to define a maximum wait time for a
response from the mail server (in seconds).

b) is/SMTP/virt_host_<*> = <host>:<port>,<port>,...;

This defines a "virtual mail host" for receiving mails. If all

incoming mails (including status notifications) are to be
received and processed in a single client of this SAP system,
this parameter is not required (an entry is/SMTP/virt_host_0 =
*:* is then assumed by default). If you want several clients
to be able to receive, you must create a virtual mail host for
every client. <host> specifies the name of the host to which
incoming mails are addressed. The "*" value can also be
specified here if the mail distribution is to occur
independently of the addressed host. Important: If the mail is
to be distributed according to host names, you must assign
different IP addresses to these host names. <port> specifies
the number of a port to which incoming mails are addressed.
Several ports may be specified for each host, and several
hosts (with several ports if necessary) may be specified for
each virtual mail host. Important: The parameter line must
always be completed with a semicolon (even if only one host is
involved). In addition, only the definition of a maximum of
100 virtual hosts is possible: virt_host_0 ... virt_host_99.
In the definition of the virtual hosts 10 to 99, warnings
occur in the kernel traces and in the parameter check in
transaction RZ10 because these parameters are unknown. You can
ignore these warnings.

The assignment of virtual mail hosts to clients is carried out in the

SAP system (see 3).

Example:

© 2020 SAP SE or an SAP affiliate company. All rights reserved 2 of 8

2020-11-19 455140

With two clients capable of receiving mail, the profile parameters could read as
follows (as of Release 6.20): icm/server_port_0 = PROT=HTTP,PORT=1080
icm/server_port_1 = PROT=HTTPS,PORT=1443
icm/server_port_2 = PROT=SMTP,PORT=25000,TIMEOUT=180
icm/server_port_3 = PROT=SMTP,PORT=25001,TIMEOUT=180
is/SMTP/virt_host_0 = *:25000;
is/SMTP/virt_host_1 = *:25001;

2. User administration (transaction SU01)

a) System users

In each client of an SAP system in which incoming mails (or status

notifications for sent mails) are to be received, a system user
must be created to process the incoming messages. To do this, use
transaction SU01 to create a user of the type "system", and assign
the "S_A.SCON" profile to this user.

Important: In Release 6.20 or lower, refer to Note 622464 regarding the

password change behavior of the system user.

b) User addresses

Each individual user who wants to receive e-mails in an SAP system

needs an Internet mail address. This is also used as a sender address
for sending e-mails. In transaction SU01, enter the Internet mail
address of a user in the field "E-Mail" under "Address". As a domain,
use the domain of the SAP system client if possible (see "General
information" above and 4.a), for example "firstname.lastname@crm-
prod.company.com".

3. Client assignment (transaction SICF)

For each client of an SAP system in which incoming mails (or status
notifications for sent mails) are to be received, and processed if
necessary, you must create an SMTP server in which the assignment to a
virtual mail host as well as the logon data is defined. In transaction SICF,
an SMTP server (envelope icon) should already be available in every SAP
system. This is delivered by SAP. Use this for the first client that you
want to be able to receive mails, and create a new SMTP server for every
other client. You must make the following settings on the SMTP servers:

a) Host data

For "Profile Parameter Number", enter the sequence number of a

parameter is/SMTP/virt_host_<*> from the profile. If you have only one
client and did not create such a parameter in the profile, enter 0.

b) Service data

Enter the client into which the mails received using this virtual mail
host are to be directed, as well as the logon data (user, password,
language) of the service user that was created for inbound mails (see
2.a).

c) Handler list

Enter CL_SMTP_EXT_SAPCONNECT in the first position.

As of Release 6.20, you must activate the SMTP server after you create or change
it (Service/Virt.Host --> Activate, or right-click).

4. SAPconnect administration (transaction SCOT)

© 2020 SAP SE or an SAP affiliate company. All rights reserved 3 of 8

2020-11-19 455140

You have to make the SAPconnect settings separately in each client from
which e-mails are to be sent or in which e-mails are to be received.

a) Default domain

The domain of this SAP system client is defined here, for example, crm-
prod.company.com. It is used for the following purposes:

• The SMTP Plug-In logs on to the mail server with the domain as ID.

• The message ID of outgoing mails is created with this domain.

• If an SAP user who has not entered an Internet mail address in their
user master record sends an e-mail, a sender address is generated from
the SAP user name and this domain, for example SMITHJ@crm-
prod.company.com.

b) Nodes

There are different types of node in SAPconnect:

• SMTP nodes (for the SMTP function of the SAP application server)

• HTTP nodes (for paging or SMS providers using Web services, as of 6.20)

• RFC nodes (for old RFC-compatible e-mail/fax/paging gateways)

There is always a single SMTP node in each client. It is created automatically

by the system and cannot be deleted. It is configured as follows (double-click
on the node name):

• Select "Node in use".

• Under "Mail Host" and "Mail Port", specify the mail server to which
outbound mails are to be transferred.

• Select "Set" for "Internet".

• Specify address areas of recipient addresses that are to be reached

using these nodes (usually "*" if all e-mails are to be sent using
SMTP).

• For "Output Formats for SAP Documents", the following is recommended:

SAPscript/Smart Forms PDF
ABAP list HTM
Business object/link HTM
RAW Text TXT

If fax messages are also to be sent using SMTP:

• Select "Set" for "Fax".

• Specify address areas of recipient addresses that are to be reached

using these nodes (usually "*" if all faxes are to be sent using SMTP).

• For "Output Formats for SAP Documents", the following is recommended:

SAPscript/Smart Forms PDF
ABAP list PDF
Business object/link TXT
RAW Text TXT

• For "Conversion into Internet Address", enter the domain of the fax
server or fax provider. The local part of the Internet address is

© 2020 SAP SE or an SAP affiliate company. All rights reserved 4 of 8

2020-11-19 455140

generated automatically by the system. The address then has the form
"FAX=+recipientnumber@domain".

If paging or SMS messages are also to be sent using SMTP:

• Select "Set" for "Pager(SMS)".

• Specify address areas of recipient addresses that are to be reached

using these nodes (usually "*" if all paging or SMS messages are to be
sent using SMTP).

• For "Conversion into Internet Address", enter the domain of the paging
or SMS server or paging or SMS provider. The local part of the Internet
address is generated automatically by the system. The address then has
the form "SMS=+recipientnumber@domain".

Important: To be able to use paging or SMS in the SAP system, names must be
defined for the messaging services to be used (e.g. "SMS"). You can do this
using transaction SA14.

c) Send job

E-mails that are sent from an SAP application are merely put into a
queue. A periodically running background process, the SAPconnect send
job, takes the e-mails from the queue and sends them by Internet. This
job can be scheduled from SAPconnect administration as follows:

• Choose "View" --> "Jobs". Check whether a job is already scheduled

(displayed as a calendar icon).

• Choose "Job" --> "Create", and specify a job name.

• Place the cursor on the "SAP&CONNECTALL" variant, and choose "Schedule

Job".

• Choose "Schedule periodically".

• Specify a time interval (for example, 10 minutes), and choose "Create".

d) Receipt

With the settings made so far, SAP users can already receive e-
mails in their inbox in the Business Workplace (transaction SBWP)
at the address entered in the user master record.

If, on receipt of e-mails to a specific address or with specific

contents (for example XML documents), you want a program that
processes these e-mails to start automatically, you can configure
this under "Settings" --> "Inbound Processing".

If, on receipt of e-mails to a specific address or from a specific

sender, you want these to be directed automatically to another
recipient or a distribution list, you can configure this under
"Settings" --> "Inbound Distribution".

5. Settings on the mail server (SAP-external configuration)

To be able to receive mails in the SAP system, you need to set your
mail server so that certain mail addresses are forwarded to one or
several SAP systems or clients. For this purpose, you need to define
routing rules that assign a mail host and/or port to address areas
(generic address parts, usually the domain), for example: *@crm-
prod.company.com --> mySAPWASHost:25000

© 2020 SAP SE or an SAP affiliate company. All rights reserved 5 of 8

2020-11-19 455140

*@crm-test.company.com --> mySAPWASHost:25001 For more information about the

exact procedure for these settings, see the mail server documentation. Note
546147 describes where the documentation can be found for the Microsoft
Exchange 2000 Server, and what to do if your mail server does not allow
routing to ports other than port 25.

Other Components

Component Description

BC-CST-IC Internet Communication Manager

This document refers to

SAP Note/KBA Title

960088 FAQ: Sending SD messages externally

833396 Notification of tester with status changes of message

779972 SURVEY: Configuration required to receive emails

622464 Change: Password change requirement for user type "SYSTEM"

607108 Problem analysis when sending or receiving e-mails

594428 SXC: Exchange 2003 Server is not supported

546147 SMTP plug-in: MS Exchange sends only to port 25

519664 Installation of SAP SEM Release 3.1B GA

519658 Upgrade to SAP SEM Release 3.1B GA

511025 Bid invitation: No confirmation of receipt

455142 SAPconnect: Configuration paging/SMS via HTTP

455129 Paging/SMS in different SAP releases

455127 E-mail (SMTP) in different SAP releases

17194 Telefax in various SAP Releases

1522754 SAP TM 8.0 - collection of notes, pro-active implementation

1455934 Notification emails not sent for CUP requests

1405426 FAQ: SI data exchange with HI funds (SHI comm server/E-Mail)

© 2020 SAP SE or an SAP affiliate company. All rights reserved 6 of 8

2020-11-19 455140
1236270 Support for SAPconnect RFC interface

1155948 SI: Configuring incoming e-mails(paying offices,DEUEV conf.)

101573 SAP Internet Mail Gateway: Versions

This document is referenced by

SAP
Title
Note/KBA

2913941 FTR: How to upload file via E-Mail

Error XS826 "Cannot process message; no node determined for..." occurs while sending in
2056291
SAPconnect

2547393 Error message XS816 'Connection refused' for SMTP messages in SOST

2841986 Sending messages via Whatsapp using SAPconnect

2656124 XS609. 450 4.7.1 Client host rejected: cannot find your hostname

2664683 Inbound email. Queue for incoming messages is active - Message no. XS098

2680180 SCOT - XS068 - Values mantained in Address Area are not saved

2623113 How to limit e-mails by Sender Group in SCOT

1702632 Authentication with user and password while sending mail through SAPconnect using SMTP

Error XS817 with text "No ESMTP Plug-In Is Available for SAPconnect" occurs in transaction SOST
1593121
while sending Mails through SMTP node

2611055 General Configuration - Offline Approval

2084590 Error "No Valid XSLT program supplied", when user evaluates the Supplier

2455624 Emails are sent intermittently from the SAP system

Troubleshooting for Alert Notification Issues with Business Process Monitoring in SAP Solution
2426954
Manager 7.1

1912890 Stuck email messages on SOST - RSCONN01 client dependent

1895298 SO672 - Still no entry in queue

2040964 Automatic login notification is not triggered when Firefighter logs in

101573 SAP Internet Mail Gateway: Versions

622464 Change: Password change requirement for user type "SYSTEM"

1522754 SAP TM 8.0 - collection of notes, pro-active implementation

© 2020 SAP SE or an SAP affiliate company. All rights reserved 7 of 8

2020-11-19 455140
1982341 E-mails are sent immediately instead of being processed in transaction SOST

1405426 FAQ: SI data exchange with HI funds (SHI comm server/E-Mail)

1236270 Support for SAPconnect RFC interface

1455934 Notification emails not sent for CUP requests

1155948 SI: Configuring incoming e-mails(paying offices,DEUEV conf.)

607108 Problem analysis when sending or receiving e-mails

960088 FAQ: Sending SD messages externally

17194 Telefax in various SAP Releases

1008835 CRM 1Order XIF: Sending a mail if a document has errors

455127 E-mail (SMTP) in different SAP releases

455129 Paging/SMS in different SAP releases

833396 Notification of tester with status changes of message

779972 SURVEY: Configuration required to receive emails

594428 SXC: Exchange 2003 Server is not supported

519658 Upgrade to SAP SEM Release 3.1B GA

519664 Installation of SAP SEM Release 3.1B GA

546147 SMTP plug-in: MS Exchange sends only to port 25

511025 Bid invitation: No confirmation of receipt

455142 SAPconnect: Configuration paging/SMS via HTTP

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2020 SAP SE or an SAP affiliate company. All rights reserved 8 of 8