SAP is going to change the e-mail infrastructure used for business e-mails sent from SAP Business ByDesign (ByD). The new e-mail infrastructure supports Domain Keys Identified Mail (DKIM), which allows you to digitally sign your business e-mails.
What are the upcoming changes?
With transition to the new e-mail infrastructure, the sending server IP and domain used to deliver e-mails sent from ByD will change.
What remains unchanged?
All other e-mail properties remain unchanged. This applies specifically to
- Envelope-from (for example email@example.com)
- Sender e-mail address (e-mail from-header) taken from your business configuration or master data settings in ByD (for example firstname.lastname@example.org)
- E-mail receiver address (e-mail to-header)
Note: The changes are not relevant for bulk e-mails in context of marketing campaigns sent from ByD, which use a DKIM supporting infrastructure already today.
What does this mean for you?
SAP takes care to create SPF records that will authorize the sending server to send e-mails using the envelope-from domains of your ByD tenants.
In case you applied additional measures using the sending server IP or sending server domain (for example IP whitelisting at e-mail receivers, spam filter configurations in your own infrastructure, or SPF records that you created in your own DNS), then you need to take action.
Such exceptions will most likely not be needed anymore when sending DKIM signed e-mails. Information on DKIM and the option to activate DKIM for your ByD systems is explained in detailed below
There are two types of E-mail scenarios in Business ByDesign:
Business E-Mails: E-mail messages sent through Tickets, customer invoice, order confirmation, etc. are all referred to business e-mail scenarios
- Here E-mails are relayed from ByD (SAP Network) – Business Mail Service Provider – Recipients.
- Business E-Mails are enabled with SPF policy only and based on request
- Business E-Mails are sent through these IP address/range – 220.127.116.11/32 ip4:18.104.22.168/32
- SPF record for the business mails are updated on the technical from/Mail From/Envelope-From address, which is always dsn@myXXXXXX.mail.sapbydesign.com or dsn@myXXXXXX.mail.sapbyd.cn
Bulk/Mass E-Mails: E-mail messages sent through Marketing/Campaign are referred as Bulk/Mass E-Mail
- Bulk E-mails are relayed from ByD (SAP Network) – Bulk Mail Service Provider – Recipients
- Bulk E-Mails are enabled with DKIM policy
- Bulk E-Mails are sent through this IP address/range – 22.214.171.124/32, 126.96.36.199/23, 188.8.131.52/27, 184.108.40.206/23, 220.127.116.11/22
- DKIM key is enabled for a customer sender domain and tenant based on request
Note – There are different service providers for business mail and for bulk mail.
Business E-Mails – E-mail messages sent through Ticket, customer invoice, order confirmation, etc. are all referred to business e-mail scenarios
- Business E-Mails are relayed from ByD (SAP Network) – CISCO Mail device (SAP Network) – Recipients
- Business E-Mails will be enabled with SPF policy by default
- Business E-Mails are sent through these IP range/address – 18.104.22.168/30, 22.214.171.124/30, 126.96.36.199/31,188.8.131.52/31
- SPF record for the business mails are updated on the technical from/Mail From/Envelop-From address, which is always
- dsn@myXXXXXX.mail.sapbydesign.com or dsn@myXXXXXX.mail.sapbyd.cn
- Example: SPF record for domain: myXXXXXX.mail.sapbydesign.com or myXXXXXX.mail.sapbyd.cn would look like: “v=spf1 include:_spf.cmail.ondemand.com ~all“
- Business E-Mails are sent with DKIM key signed – This is done based on “Explicit Request“, how to request DKIM key for your sender domains that are used in ByD sending Business E-Mails is mentioned below
Example: DKIM record for sender domain looks like:
Bulk/Mass E-Mails – The bulk E-Mail scenario remains the same for now.
- How to request DKIM key for your E-Mail sender domain address?
Please create an incident to SAP Business ByDesign Support providing the below mentioned details
Subject: Request to enable DKIM for Business E-Mails
Content of the Incident:
- Sender Domain address details that is used from your tenant to relay Business Mails (Example: test.com, abc.uk for scenarios like Tickets, customer invoice, order confirmation, etc.)
NOTE 1 – In case if you have multiple domains, please provide the complete list (Including Sub-Domains if any)
NOTE 2 – A common DKIM key is generated if there are multiple domains
- Execution steps for enabling DKIM Key?
The Service Request takes approximately 2 weeks of time for enabling and implementing
- Once we get the domain details as mentioned in FAQ’s section point 1
- DKIM key will be generated from our side (with Key Size – 1024 Bit)
- Public Key and Selector details will be shared to customer
- Customer must create a DKIM TXT record in their DNS Servers
NOTE: In case if you have multiple domains, please mention all the domains name, and only one key is provided by default for all the domains. Maintain the same DKIM key for all the domains.
- Check if the key is maintained correctly through external tools by providing the “Domain” and “Selector” details
- Once the key is correctly maintained, send the incident back to SAP for activating the key.
- SAP will activate the key for the mentioned domains and will close the incident.
- What is DKIM and Advantages of enabling DKIM key for Business Mails?
DKIM (Domain Keys Identified Mail) is an e-mail authentication technique that allows the receiver to
check that an email was indeed send and authorized by the owner of that domain. This is done by
giving the email a digital signature. This DKIM signature is a header that is added to the message and is secured with encryption.
- Implementing DKIM will improve email deliverability
- Prevents from E-mail spoofing
- Makes mails trustworthy
- What is SPF and Advantages of enabling SPF record for Business Mails?
The Sender Policy Framework (SPF) is an email-authentication technique which is used to prevent spammers from sending messages on behalf of your domain. The SPF record is checked on “Envelope-From/Mail-From/Technical Sender” address
- By enabling this it is determined which e-mail servers are authorized to relay an e-mail.
- How to check SPF record?
Use any External Tool like https://mxtoolbox.com/SuperTool.aspx → Provide the domain as myXXXXXX.mail.sapbydesign.com or myXXXXXX.mail.sapbyd.cn
- How to check DKIM key for a sender domain once DKIM TXT record is updated in your DNS Servers?
External Tool like https://dkimcore.org/tools/keycheck.html → Provide the “Selector” and “Domain” details → click on button “Check”, You should be seeing a record similar to below
- SPF and DKIM policies are checked on which domains for Outbound Mail Scenario?
These checks are done at recipient Mail Server, in general mails sent from SAP Business ByDesign application have headers similar to the following:
SPF Check is done on – “Envelop-From” address
DKIM Check is done on – “From Address”
Recipient Address: <Independent details>
Subject: <Independent details>
- Can the “Envelop-From” address be overwritten to the same as “From Address”
NO, this is not possible and not supported in the solution
From Address: <>@abc.com
Envelope-From Address: <>@abc.com
- Can the customer point their ByD tenant to their own Mail infrastructure?
NO, this is not possible and not supported in SAP Business ByDesign.
- In case of special request or any queries which are not covered above
Please create an incident to SAP Business ByDesign Support
- What is the size limit of an Outbound and Inbound E-mail sent/received at SAP Business ByDesign application?
Mail size can be maximum of 25MB (Including attachments)
- How to check if e-mail messages sent from SAP Business ByDesign Tenant is DKIM signed, and for which domain is it DKIM signed?
Check the mail headers: “header.i”, “header.s”, “header.from” of the received E-Mail, in the section “Authentication-Results”: In this section we should see the domain and selector details of the DKIM key.
- Whether mail is relayed securely from our mail relay server(CISCO)
Yes, the E-Mail is relayed securely with TLSv1.2 protocol by default, and incase if the target/recipient mail infra doesn’t support TLSv1.2 protocol a fall back protocol is used.
NOTE: It is currently recommended to ensure that your mail servers support TLSv1.2 protocol because in future TLSv1.1 and TLSv1.0 will be disabled.
- What are the attachment types that are “NOT Allowed” at our CISCO mail server?
E-mails containing one of the following file types currently fall into the category “dangerous attachment”:
ade, adp, app, asp, bas, bat, bhx, cab, ceo, chm, cmd, com, cpl, crt, csr, der, exe, fxp, hlp, hta, inf, ins, isp, its, js, jse, lnk, mad, maf, mag, mam, mar, mas, mat, mde, mim, msc, msi, msp, mst, ole, pcd, pif, reg, scr, sct, shb, shs, vb, vbe, vbmacros, vbs, vsw, wmd, wmz, ws, wsc, wsf, wsh, xxe, docm, xlsm
This also applies if attachments with these extensions are found in the following (password-protected) archives:
arj, cab, jar, lha, rar, tar, zip, gz
- Can customer choose their own selector while requesting a DKIM key?
A standard and unique selector is provided for each customers domain(s) so it is not possible to deliver the DKIM keys with custom selectors that are requested by Customers
- In case if you have any throttling on your E-Mail server based on IP address (Like – How many E-mails can be sent in a period?)
You should whitelist following IP addresses at your side: 184.108.40.206/30, 220.127.116.11/30, 18.104.22.168/31,22.214.171.124/31
- What is the IP address through which E-Mails are sent from your ByD tenant?
Following are the IP address through which your E-Mails will be sent from your ByD tenant: 126.96.36.199/30, 188.8.131.52/30, 184.108.40.206/31,220.127.116.11/31
We hope that this article provides clarity on migration of ByD customers to the new E-mail infrastructure, which is more reliable and secure.